streamline descriptions, fix formatting & add redirects

add redirects to group sections in nginx.conf
streamline descriptions by moving shared parts to grouping introductions
fix formatting
remove HTML when possible

Author: TC-MO

apify-api/openapi/paths/actor-runs/actor-runs@{runId}@charge.yaml

@@ -9,7 +9,7 @@ post:
 
     :::note
 
-    Note that pay per events Actors are still in alpha. Please, reach out to us with any questions or feedback.
+    Pay per events Actors are still in alpha. Please, reach out to us with any questions or feedback.
 
     :::
   operationId: PostChargeRun

apify-api/openapi/paths/actor-runs/actor-runs@{runId}@metamorph.yaml

@@ -18,8 +18,7 @@ post:
     All the default storages are preserved and the new input is stored under the
     `INPUT-METAMORPH-1` key in the same default key-value store.
 
-    For more information, see the [Actor
-    docs](https://docs.apify.com/platform/actors/development/programming-interface/metamorph).
+    For more information, see the [Actor docs](https://docs.apify.com/platform/actors/development/programming-interface/metamorph).
   operationId: actorRun_metamorph_post
   parameters:
     - name: runId

apify-api/openapi/paths/actor-runs/actor-runs@{runId}@resurrect.yaml

@@ -8,8 +8,7 @@ post:
     Run status will be updated to RUNNING and its container will be restarted with the same storages
     (the same behaviour as when the run gets migrated to the new server).
 
-    For more information,
-    see the [Actor docs](https://docs.apify.com/platform/actors/running/runs-and-builds#resurrection-of-finished-run).
+    For more information, see the [Actor docs](https://docs.apify.com/platform/actors/running/runs-and-builds#resurrection-of-finished-run).
   operationId: PostResurrectRun
   parameters:
     - name: runId

apify-api/openapi/paths/actor-tasks/actor-tasks.yaml

@@ -3,8 +3,9 @@ get:
     - Actor tasks
   summary: Get list of tasks
   description: |
-    Gets the complete list of tasks that a user has created or used. The
-    response is a list of objects in which each object contains essential
+    Gets the complete list of tasks that a user has created or used.
+
+    The response is a list of objects in which each object contains essential
     information about a single task.
 
     The endpoint supports pagination using the `limit` and `offset` parameters,

apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}@run-sync-get-dataset-items.yaml

@@ -1,21 +1,14 @@
-post:
+get:
   tags:
     - Actor tasks
-  summary: Run task synchronously and get dataset items (POST)
+  summary: Run task synchronously and get dataset items
   description: |
-    Runs an Actor task and synchronously returns its dataset items.
+    Run a specific task and return its dataset items.
 
     The run must finish in 300<!-- MAX_ACTOR_JOB_SYNC_WAIT_SECS --> seconds
     otherwise the HTTP request fails with a timeout error (this won't abort
     the run itself).
 
-    Optionally, you can override the Actor input configuration by passing a JSON
-    object as the POST payload and setting the `Content-Type: application/json` HTTP header.
-
-    Note that if the object in the POST payload does not define a particular
-    input property, the Actor run uses the default value defined by the task (or the Actor's
-    input schema if not defined by the task).
-
     You can send all the same options in parameters as the [Get Dataset
     Items](#/reference/datasets/item-collection/get-items) API endpoint.
 
@@ -26,15 +19,10 @@ post:
     If the connection breaks, you will not receive any information about the run
     and its status.
 
-    Input fields from Actor task configuration can be overloaded with values
-    passed as the POST payload.
-
-    Just make sure to specify the `Content-Type` header as `application/json`
-    and that the input is an object.
-
-    To run the task asynchronously, use the [Run
-    task](#/reference/actor-tasks/run-collection/run-task) API endpoint instead.
-  operationId: actorTask_runSyncGetDatasetItems_post
+    To run the Task asynchronously, use the [Run task
+    asynchronously](#/reference/actor-tasks/run-collection/run-task) endpoint
+    instead.
+  operationId: actorTask_runSyncGetDatasetItems_get
   parameters:
     - name: actorTaskId
       in: path
@@ -96,11 +84,9 @@ post:
       in: query
       description: |
         Specifies optional webhooks associated with the Actor run, which can be
-        used to receive a notification
-        e.g. when the Actor finished or failed. The value is a Base64-encoded
+        used to receive a notification e.g. when the Actor finished or failed. The value is a Base64-encoded
         JSON array of objects defining the webhooks. For more information, see
-        [Webhooks
-        documentation](https://docs.apify.com/platform/integrations/webhooks).
+        [Webhooks documentation](https://docs.apify.com/platform/integrations/webhooks).
       style: form
       explode: true
       schema:
@@ -121,9 +107,12 @@ post:
       description: |
         If `true` or `1` then the API endpoint returns only non-empty items and
         skips hidden fields
+
         (i.e. fields starting with the # character).
+
         The `clean` parameter is just a shortcut for `skipHidden=true` and
         `skipEmpty=true` parameters.
+
         Note that since some objects might be skipped from the output, that the
         result might contain less items than the `limit` value.
       style: form
@@ -155,9 +144,12 @@ post:
       in: query
       description: |
         A comma-separated list of fields which should be picked from the items,
+
         only these fields will remain in the resulting record objects.
+
         Note that the fields in the outputted items are sorted the same way as
         they are specified in the `fields` query parameter.
+
         You can use this feature to effectively fix the output format.
       style: form
       explode: true
@@ -177,13 +169,18 @@ post:
       description: |
         A comma-separated list of fields which should be unwound, in order which
         they should be processed. Each field should be either an array or an object.
+
         If the field is an array then every element of
+
         the array will become a separate record and merged with parent object.
+
         If the unwound field is an object then it is merged with the parent
         object
+
         If the unwound field is missing or its value is neither an array nor an
         object and therefore cannot be merged with a parent object then the item
         gets preserved as it is.
+
         Note that the unwound items ignore the `desc` parameter.
       style: form
       explode: true
@@ -195,8 +192,10 @@ post:
       description: |
         A comma-separated list of fields which should transform nested objects
         into flat structures.
+
         For example, with `flatten="foo"` the object `{"foo":{"bar": "hello"}}`
         is turned into `{"foo.bar": "hello"}`.
+
         The original object with properties is replaced with the flattened
         object.
       style: form
@@ -241,8 +240,10 @@ post:
       description: |
         All text responses are encoded in UTF-8 encoding. By default, the
         `format=csv` files are prefixed with
+
         the UTF-8 Byte Order Mark (BOM), while `json`, `jsonl`, `xml`, `html`
         and `rss` files are not.
+
         If you want to override this default behavior, specify `bom=1` query
         parameter to include the BOM or `bom=0` to skip it.
       style: form
@@ -305,10 +306,8 @@ post:
       description: |
         If `true` or `1` then, the endpoint applies the
         `fields=url,pageFunctionResult,errorInfo`
-
         and `unwind=pageFunctionResult` query parameters. This feature is used
         to emulate simplified results provided by the
-
         legacy Apify Crawler product and it's not recommended to use it in new
         integrations.
       style: form
@@ -321,7 +320,6 @@ post:
       description: |
         If `true` or `1` then, the all the items with errorInfo property will be
         skipped from the output.
-
         This feature is here to emulate functionality of API version 1 used for
         the legacy Apify Crawler product and it's not recommended to use it in
         new integrations.
@@ -330,15 +328,6 @@ post:
       schema:
         type: boolean
         example: false
-  requestBody:
-    description: ''
-    content:
-      application/json:
-        schema:
-          type: object
-        example:
-          foo: bar
-    required: true
   responses:
     '201':
       description: ''
@@ -378,22 +367,36 @@ post:
         application/json:
           schema:
             $ref: "../../components/schemas/common/ErrorResponse.yaml"
+    '408':
+      description: 'Request Timeout: the HTTP request exceeded the 300 second limit'
+      headers: {}
+      content:
+        application/json:
+          schema:
+            $ref: "../../components/schemas/common/ErrorResponse.yaml"
   deprecated: false
   x-legacy-doc-urls:
-    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items/run-task-synchronously-and-get-dataset-items-post
-    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items-post
-    - https://docs.apify.com/api/v2#tag/Actor-tasksRun-task-synchronously-and-get-dataset-items/operation/actorTask_runSyncGetDatasetItems_post
-get:
+    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items/run-task-synchronously-and-get-dataset-items-get
+    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items-get
+    - https://docs.apify.com/api/v2#tag/Actor-tasksRun-task-synchronously-and-get-dataset-items/operation/actorTask_runSyncGetDatasetItems_get
+post:
   tags:
     - Actor tasks
-  summary: Run task synchronously and get dataset items (GET)
+  summary: Run task synchronously and get dataset items
   description: |
-    Run a specific task and return its dataset items.
+    Runs an Actor task and synchronously returns its dataset items.
 
     The run must finish in 300<!-- MAX_ACTOR_JOB_SYNC_WAIT_SECS --> seconds
     otherwise the HTTP request fails with a timeout error (this won't abort
     the run itself).
 
+    Optionally, you can override the Actor input configuration by passing a JSON
+    object as the POST payload and setting the `Content-Type: application/json` HTTP header.
+
+    Note that if the object in the POST payload does not define a particular
+    input property, the Actor run uses the default value defined by the task (or the Actor's
+    input schema if not defined by the task).
+
     You can send all the same options in parameters as the [Get Dataset
     Items](#/reference/datasets/item-collection/get-items) API endpoint.
 
@@ -404,10 +407,15 @@ get:
     If the connection breaks, you will not receive any information about the run
     and its status.
 
-    To run the Task asynchronously, use the [Run task
-    asynchronously](#/reference/actor-tasks/run-collection/run-task) endpoint
-    instead.
-  operationId: actorTask_runSyncGetDatasetItems_get
+    Input fields from Actor task configuration can be overloaded with values
+    passed as the POST payload.
+
+    Just make sure to specify the `Content-Type` header as `application/json`
+    and that the input is an object.
+
+    To run the task asynchronously, use the [Run
+    task](#/reference/actor-tasks/run-collection/run-task) API endpoint instead.
+  operationId: actorTask_runSyncGetDatasetItems_post
   parameters:
     - name: actorTaskId
       in: path
@@ -470,10 +478,8 @@ get:
       description: |
         Specifies optional webhooks associated with the Actor run, which can be
         used to receive a notification
-
         e.g. when the Actor finished or failed. The value is a Base64-encoded
         JSON array of objects defining the webhooks. For more information, see
-
         [Webhooks
         documentation](https://docs.apify.com/platform/integrations/webhooks).
       style: form
@@ -496,12 +502,9 @@ get:
       description: |
         If `true` or `1` then the API endpoint returns only non-empty items and
         skips hidden fields
-
         (i.e. fields starting with the # character).
-
         The `clean` parameter is just a shortcut for `skipHidden=true` and
         `skipEmpty=true` parameters.
-
         Note that since some objects might be skipped from the output, that the
         result might contain less items than the `limit` value.
       style: form
@@ -533,12 +536,9 @@ get:
       in: query
       description: |
         A comma-separated list of fields which should be picked from the items,
-
         only these fields will remain in the resulting record objects.
-
         Note that the fields in the outputted items are sorted the same way as
         they are specified in the `fields` query parameter.
-
         You can use this feature to effectively fix the output format.
       style: form
       explode: true
@@ -558,18 +558,13 @@ get:
       description: |
         A comma-separated list of fields which should be unwound, in order which
         they should be processed. Each field should be either an array or an object.
-
         If the field is an array then every element of
-
         the array will become a separate record and merged with parent object.
-
         If the unwound field is an object then it is merged with the parent
         object
-
         If the unwound field is missing or its value is neither an array nor an
         object and therefore cannot be merged with a parent object then the item
         gets preserved as it is.
-
         Note that the unwound items ignore the `desc` parameter.
       style: form
       explode: true
@@ -581,10 +576,8 @@ get:
       description: |
         A comma-separated list of fields which should transform nested objects
         into flat structures.
-
         For example, with `flatten="foo"` the object `{"foo":{"bar": "hello"}}`
         is turned into `{"foo.bar": "hello"}`.
-
         The original object with properties is replaced with the flattened
         object.
       style: form
@@ -629,10 +622,8 @@ get:
       description: |
         All text responses are encoded in UTF-8 encoding. By default, the
         `format=csv` files are prefixed with
-
         the UTF-8 Byte Order Mark (BOM), while `json`, `jsonl`, `xml`, `html`
         and `rss` files are not.
-
         If you want to override this default behavior, specify `bom=1` query
         parameter to include the BOM or `bom=0` to skip it.
       style: form
@@ -695,8 +686,10 @@ get:
       description: |
         If `true` or `1` then, the endpoint applies the
         `fields=url,pageFunctionResult,errorInfo`
+
         and `unwind=pageFunctionResult` query parameters. This feature is used
         to emulate simplified results provided by the
+
         legacy Apify Crawler product and it's not recommended to use it in new
         integrations.
       style: form
@@ -709,6 +702,7 @@ get:
       description: |
         If `true` or `1` then, the all the items with errorInfo property will be
         skipped from the output.
+
         This feature is here to emulate functionality of API version 1 used for
         the legacy Apify Crawler product and it's not recommended to use it in
         new integrations.
@@ -717,6 +711,15 @@ get:
       schema:
         type: boolean
         example: false
+  requestBody:
+    description: ''
+    content:
+      application/json:
+        schema:
+          type: object
+        example:
+          foo: bar
+    required: true
   responses:
     '201':
       description: ''
@@ -756,15 +759,8 @@ get:
         application/json:
           schema:
             $ref: "../../components/schemas/common/ErrorResponse.yaml"
-    '408':
-      description: 'Request Timeout: the HTTP request exceeded the 300 second limit'
-      headers: {}
-      content:
-        application/json:
-          schema:
-            $ref: "../../components/schemas/common/ErrorResponse.yaml"
   deprecated: false
   x-legacy-doc-urls:
-    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items/run-task-synchronously-and-get-dataset-items-get
-    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items-get
-    - https://docs.apify.com/api/v2#tag/Actor-tasksRun-task-synchronously-and-get-dataset-items/operation/actorTask_runSyncGetDatasetItems_get
+    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items/run-task-synchronously-and-get-dataset-items-post
+    - https://docs.apify.com/api/v2#/reference/actor-tasks/run-task-synchronously-and-get-dataset-items-post
+    - https://docs.apify.com/api/v2#tag/Actor-tasksRun-task-synchronously-and-get-dataset-items/operation/actorTask_runSyncGetDatasetItems_post