```suggestion | `pagination[start]` | Integer | Start value (i.e. first entry to return) | 0 | ```

```suggestion To paginate results by offset, use the following parameters: ```

```suggestion To paginate results by page, use the following parameters: ```

```suggestion The `population` parameter is used to explicitly define which Dynamic zones, components, and nested components to populate. ```

Please rephrase to avoid using "you" and remove the "See the following… " sentence :-)

I would either remove the "role based" parenthesis or be more explicit, it's not super clear to me.

```suggestion It's currently not possible to return just an array of IDs. This is something that is currently under discussion. ```

```suggestion By default Strapi will not populate any type of fields. ```

Please combine the cautions and use a bullet list: ::: caution * [content for caution 1] * [content for caution 2]

Please use lowercase :-)

Same comment about "normal". We should be more explicit.

```suggestion :::tip ```

Not sure we should use "normal". We should be more specific. What's a 'normal` field? Suggestion: "By default, only the following types of fields are returned: [ insert types that are returned here]. Fields selection does not work on relational, media, component, or dynamic zone fields. Use [population](#population) instead.

```suggestion * Relations, media fields, components, and dynamic zones are not populated by default. Use the `populate` parameter to populate these data structures (see [population documentation](/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md#population)) * It is not possible to filter on dynamic zones or media fields. ``` 2 distinct ideas + casing + formatting/consistency with other links (see [handbook](https://handbook.strapi.io/user-success-manual/strapi-documentation-style-guide#7d0e888be1964efb96428ba804be4003) :-) )

```suggestion :::note ```

```suggestion Complex filtering is combining multiple filters utilizing advanced methods such as combining `$and` & `$or`. This allows for more flexibility to request exactly the data needed. ``` Tone of voice - we try to stay neutral

```suggestion ### Complex filtering ``` Styleguide - We don't title case every word in h2/h3/h4 headings

```suggestion The [REST API](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md) offers the ability to filter results found with its ["Get entries"](/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md#get-entries) method.<br/> Using optional Strapi features can provide some more filters: * If the [Internationalization (i18n) plugin](/developer-docs/latest/plugins/i18n.md) is enabled on a content-type, it's possible to filter by locale. * If the [Draft & Publish](/developer-docs/latest/concepts/draft-and-publish.md) is enabled, it's possible to filter based on a `live` or `draft` state. ``` Cleaner look (using lists) when we have multiple possibilities + avoid using "you" (neutral tone, see our Handbook > 12 rules)

```suggestion | `locale` | String/Array | [Select one ore multiple locales](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#locale) | ``` As there are multiple options available, I'd rather not list them in the description (contrary to the line above, re. publication state, where we only have 2 options).

```suggestion | `publicationState` | String | [Select the draft & publish state](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#publication-state)<br/><br/>Only accepts the following values:<ul><li>`live`</li><li>`preview`</li></ul> | ``` (for consistency with some other tables in the documentation)

```suggestion | `filters` | Object | [Filter the response](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#filtering) | ``` for consistency with other action verbs in the table (same for the line above) :-)

```suggestion [API parameters](#api-parameters) can be used to [filter](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#filtering), [sort](/developer-docs/latest/developer-resources/database-apis-reference/rest/sort-pagination.md#sorting), and [paginate](/developer-docs/latest/developer-resources/database-apis-reference/rest/sort-pagination.md#pagination) results and to [select fields](/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md#field-selection) and relations to [populate](/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md#population)). Additionally, specific parameters related to optional Strapi features can be used, like [publication state](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#publication-state) and [locale](/developer-docs/latest/developer-resources/database-apis-reference/rest/filtering-locale-publication.md#locale. ``` ;-) (unwanted parenthesis)

I would recommend you keep the original link, as the intent was to explain that `not` can be used either as a logical operator or as an attribute operator. (I know this is detected as a missing link by the `check-links` script but this is a false positive. You can use the `checklinksIgnoredFiles` array in VuePress' `config.js` if you want to ignore this file :-)

```suggestion // ... ```

```suggestion // ... ```

```suggestion // ... ```

```suggestion // ... ```

Great idea, thanks! I'd suggest you add links to sub-headings, as suggested in this example: ```suggestion | [`sort`](#sorting) | String/Array | Sorting the response | ```

Your suggested change is because we're not using `?populate=categories`, here, right? Thank you, good catch!