Should move the "If omitted" as the last sentence. Otherwise, are we talking about the "set to true" option here? Or the option to omit?

Should be "If omitted" to be consistent

I believe this looks "darkened" because you have both the code class endpt AND also backticks. It should only be the code class endpt

should be lowercase

This is the section where we should move the wildcard paragraph to, from the "LongText Field Type" section

OMG there is a perfect place to put this now! We should move this paragraph to the LIKE section, under the WHERE clause of Syntax & Structure

code styling typo

code taga

code taga

code tags?

Maybe an example of something that would not work? Because it kind of looks like there is an OR in a where clause below

I think only the "=" should be in code tags? Because "=" is the operator, "Equal to" is just a description.

I actually don't think we need this description at all, because we have a description column. We can neaten this column up to just have the operator

I would link this or remove it

Is there a reason "Field" is capitalized here? In the SELECT example it is not capitalized

code styling? (omitting commas)

code styling?

code styling?

code styling?

code styling?

code styling?

code styling

v17.1

remove italics

this should be lowercase, but again this is a nice to have

we could use the "success" styling here instead to make this green... nice to have, not urgent

lowercase v

Maybe we should just say "Vault Objects are divided into the following categories:"

Because it says "three" here and clearly there are more than three. Also I think putting objects in quotes like this may be confusing?

Maybe add a bullet here to learn more about API rate limits?

We have a nice detsiled section about it in the API reference: https://internal-developer.veevavault.com/docs/#api-rate-limits

we should mention this is called "Daily Limit".

we should mention this is called "Burst Limit".

code styling instead of bold?

code styling instead of bold?

code styling instead of bold?

code styling instead of bold?

There is an open quote here, so I think this needs an end quote?

Maybe we should indent this bullet? Because it's kind of like a sub-bullet to the first one? An example

Good examples here! Very easy to understand

I've written this word a few times and I am not hyphenating it. I think we should standardize to use no hyphen (unless you want to fight - I mean discuss this with me :P)

I think we should remove this word?

needs closing quotes

is there a space between these words?

maybe no italics here?

code tag here

I don't know what latest version vs absolute latest version means

Code highlighting error

Code highlighting error

Code highlighting error

Maybe the table or lead-in sentence to the table above should mention this document name?

Should this be "Version Description" instead of Notes? When a user creates a new version, there is a description just for this version called Version Description

does this mean they use LATESTVERSION by default?

Similar comment here that this isn't ended properly, it looks cut off

I'm not sure why this isn't "label__v"

These should be "straight quotes" rather than curly quotes

Should this have a comma after it? Kind of like starting a sentence with "After" or "Next", I think they're always supposed to have a comma. But I agree with the comma it still looks weird.

Maybe we can re-write this to say "For example, perhaps you want to create a query on the id field. To check if this field is queryable, we need to call the metadata API as shown in the example below. The response shows..."

Oddly, this is the first time the reader encounters this term. I think this is synonymous with "VQL"?

In the first overview paragraph we should mention this term to make sure readers know what this is

this link does not work (looks like wrong ID)

a comma indiates there is more to come (a comma like this at the end would cause a syntax error). We should also end the quare bracket we opened previously

I believe this should be:

"file 2"}]

If we are including the opening bracket here, we should have a closing bracket at the end as well

should this be label__v?

The example below this does not display additional syntax. Maybe we want to end this sentence, and have a new sentence which says "The following is a skeleton for a VQL query:" or similar?

I think this comma should be removed? Something about this sentence is not making sense

The parens seem out of place here. Maybe we can just omit them?

Needs ending curly brace ( } )

Should be lowercase "v"