fix Actor capilatization

Author: TC-MO

apify-api/openapi/components/tags.yaml

@@ -8,12 +8,12 @@
   - '#/reference/actors/actor-object'
   - '#tag/ActorsActor-object'
   description: |
-    The API endpoints described in this section enable you to manage, build and run Apify actors.
+    The API endpoints described in this section enable you to manage, build and run Apify Actors.
     For more information, see the <a href="https://docs.apify.com/platform/actors">Actor documentation</a>.
 
-    Note that for all the API endpoints that accept the `actorId` parameter to specify an actor,
-    you can pass either the actor ID (e.g. `HG7ML7M8z78YcAPEB`) or a tilde-separated
-    username of the actor owner and the actor name (e.g. `janedoe~my-actor`).
+    Note that for all the API endpoints that accept the `actorId` parameter to specify an Actor,
+    you can pass either the Actor ID (e.g. `HG7ML7M8z78YcAPEB`) or a tilde-separated
+    username of the Actor owner and the Actor name (e.g. `janedoe~my-actor`).
 
     Some of the API endpoints return runs objects. Note that if any such run object
     contains usage in dollars, your effective unit pricing at the time of query
@@ -77,7 +77,7 @@
       </tr>
     </table>
 
-    For more information about source code and actor versions, see [Source code](https://docs.apify.com/platform/actors/development/actor-definition/source-code)
+    For more information about source code and Actor versions, see [Source code](https://docs.apify.com/platform/actors/development/actor-definition/source-code)
     in Actors documentation.
 - name: Actors/Actor builds
   x-displayName: Actor builds
@@ -121,20 +121,20 @@
   x-trait: 'true'
   description: |
     This is not a single endpoint, but an entire group of endpoints that lets you to
-    retrieve and manage the last run of given actor or any of its default storages.
+    retrieve and manage the last run of given Actor or any of its default storages.
     All the endpoints require an authentication token.
 
     The endpoints accept the same HTTP methods and query parameters as
     the respective storage endpoints.
-    The base path represents the last actor run object is:
+    The base path represents the last Actor run object is:
 
     `/v2/acts/{actorId}/runs/last{?token,status}`
 
     Using the `status` query parameter you can ensure to only get a run with a certain status
     (e.g. `status=SUCCEEDED`). The output of this endpoint and other query parameters
     are the same as in the [Run object](#/reference/actors/run-object) endpoint.
 
-    In order to access the default storages of the last actor run, i.e. log, key-value
+    In order to access the default storages of the last Actor run, i.e. log, key-value
     store, dataset and request queue, use the following endpoints:
 
     * `/v2/acts/{actorId}/runs/last/log{?token,status}`
@@ -166,7 +166,7 @@
     [Request collection](#/reference/request-queues/request)
     * `/v2/acts/{actorId}/runs/last/request-queue/head{?token,status}` [Queue head](#/reference/request-queues/queue-head)
 
-    For example, to download data from a dataset of the last succeeded actor run in XML format,
+    For example, to download data from a dataset of the last succeeded Actor run in XML format,
     send HTTP GET request to the following URL:
 
     ```
@@ -188,7 +188,7 @@
   - '#/reference/actor-builds/build-log'
   - '#tag/Actor-buildsBuild-log'
   description: |
-    The API endpoints described in this section enable you to manage Apify actor builds.
+    The API endpoints described in this section enable you to manage Apify Actor builds.
 
     Note that if any returned build object contains usage in dollars, your effective
     unit pricing at the time of query has been used for computation of this dollar equivalent, and hence it should be
@@ -218,7 +218,7 @@
     This section describes API endpoints to manage Key-value stores.
     Key-value store is a simple storage for saving and reading data records or files.
     Each data record is represented by a unique key and associated with a MIME content type.
-    Key-value stores are ideal for saving screenshots, actor inputs and outputs, web pages,
+    Key-value stores are ideal for saving screenshots, Actor inputs and outputs, web pages,
     PDFs or to persist the state of crawlers.
     For more information, see the <a href="https://docs.apify.com/platform/storage/key-value-store">Key-value
     store documentation</a>.
@@ -247,7 +247,7 @@
   - '#/reference/actor-tasks/last-run-object-and-its-storages'
   - '#tag/Actor-tasksLast-run-object-and-its-storages'
   description: |
-    The API endpoints described in this section enable you to manage and run Apify actor tasks.
+    The API endpoints described in this section enable you to manage and run Apify Actor tasks.
     For more information, see the <a href="https://docs.apify.com/platform/actors/running/tasks">Actor
     tasks documentation</a>.
 
@@ -308,7 +308,7 @@
     This section describes API endpoints to manage Key-value stores.
     Key-value store is a simple storage for saving and reading data records or files.
     Each data record is represented by a unique key and associated with a MIME content type.
-    Key-value stores are ideal for saving screenshots, actor inputs and outputs, web pages,
+    Key-value stores are ideal for saving screenshots, Actor inputs and outputs, web pages,
     PDFs or to persist the state of crawlers.
     For more information, see the <a href="https://docs.apify.com/platform/storage/key-value-store">Key-value
     store documentation</a>.
@@ -380,7 +380,7 @@
     Webhooks provide an easy and reliable way to configure the Apify platform
     to carry out an action (e.g. a HTTP request to another service) when a certain
     system event occurs.
-    For example, you can use webhooks to start another actor when an actor run finishes
+    For example, you can use webhooks to start another Actor when an Actor run finishes
     or fails.
     For more information see <a href="https://docs.apify.com/platform/integrations/webhooks">Webhooks
     documentation</a>.
@@ -409,9 +409,9 @@
   description: |
     This section describes API endpoints for managing schedules.
 
-    Schedules are used to automatically start your actors at certain times. Each schedule
-    can be associated with a number of actors and actor tasks. It is also possible
-    to override the settings of each actor (task) similarly to when invoking the actor
+    Schedules are used to automatically start your Actors at certain times. Each schedule
+    can be associated with a number of Actors and Actor tasks. It is also possible
+    to override the settings of each Actor (task) similarly to when invoking the Actor
     (task) using the API.
     For more information, see <a href="https://docs.apify.com/platform/schedules">Schedules
     documentation</a>.
@@ -443,11 +443,11 @@
   - '#tag/LogsLog'
   description: |
     The API endpoints described in this section are used the download the logs
-    generated by actor builds and runs. Note that only the trailing 5M characters
+    generated by Actor builds and runs. Note that only the trailing 5M characters
     of the log are stored, the rest is discarded.
 
     Note that the endpoints do not require the authentication token, the calls
-    are authenticated using a hard-to-guess ID of the actor build or run.
+    are authenticated using a hard-to-guess ID of the Actor build or run.
   x-trait: true
 - name: Users
   x-displayName: Users

apify-api/openapi/openapi.yaml

@@ -66,39 +66,39 @@ info:
     ## Basic usage
     <span id="/introduction/basic-usage"></span>
 
-    To run an actor, send a POST request to the [Run
-    actor](#/reference/actors/run-collection/run-actor) endpoint using either the
-    actor ID code (e.g. `vKg4IjxZbEYTYeW8T`) or its name (e.g.
+    To run an Actor, send a POST request to the [Run
+    Actor](#/reference/actors/run-collection/run-actor) endpoint using either the
+    Actor ID code (e.g. `vKg4IjxZbEYTYeW8T`) or its name (e.g.
     `janedoe~my-actor`):
 
     `https://api.apify.com/v2/acts/[actor_id]/runs`
 
-    If the actor is not runnable anonymously, you will receive a 401 or 403
+    If the Actor is not runnable anonymously, you will receive a 401 or 403
     [response code](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status).
     This means you need to add your [secret API
     token](https://console.apify.com/account#/integrations) to the request's
     `Authorization` header ([recommended](#/introduction/authentication)) or as a
     URL query parameter `?token=[your_token]` (less secure).
 
     Optionally, you can include the query parameters described in the [Run
-    actor](#/reference/actors/run-collection/run-actor) section to customize your
+    Actor](#/reference/actors/run-collection/run-actor) section to customize your
     run.
 
-    If you're using Node.js, the best way to run an actor is using the
+    If you're using Node.js, the best way to run an Actor is using the
     `Apify.call()` method from the [Apify
     SDK](https://sdk.apify.com/docs/api/apify#apifycallactid-input-options). It
-    runs the actor using the account you are currently logged into (determined
+    runs the Actor using the account you are currently logged into (determined
     by the [secret API token](https://console.apify.com/account#/integrations)).
-    The result is an [actor run
+    The result is an [Actor run
     object](https://sdk.apify.com/docs/typedefs/actor-run) and its output (if
     any).
 
     A typical workflow is as follows:
 
-    1. Run an actor or task using the [Run
-    actor](#/reference/actors/run-collection/run-actor) or [Run
+    1. Run an Actor or task using the [Run
+    Actor](#/reference/actors/run-collection/run-actor) or [Run
     task](#/reference/actor-tasks/run-collection/run-task) API endpoints.
-    2. Monitor the actor run by periodically polling its progress using the [Get
+    2. Monitor the Actor run by periodically polling its progress using the [Get
     run](#/reference/actor-runs/run-object-and-its-storages/get-run) API
     endpoint.
     3. Fetch the results from the [Get
@@ -109,7 +109,7 @@ info:
     using the `defaultKeyValueStoreId` and the store's `key`.
 
     **Note**: Instead of periodic polling, you can also run your
-    [actor](#/reference/actors/run-actor-synchronously) or
+    [Actor](#/reference/actors/run-actor-synchronously) or
     [task](#/reference/actor-tasks/runs-collection/run-task-synchronously)
     synchronously. This will ensure that the request waits for 300 seconds (5
     minutes) for the run to finish and returns its output. If the run takes
@@ -151,7 +151,7 @@ info:
 
     All API endpoints that return a list of records
     (e.g. [Get list of
-    actors](#/reference/actors/actor-collection/get-list-of-actors))
+    Actors](#/reference/actors/actor-collection/get-list-of-actors))
     enforce pagination in order to limit the size of their responses.
 
     Most of these API endpoints are paginated using the `offset` and `limit`
@@ -417,10 +417,10 @@ info:
       operations on key-value store records
 
     These endpoints have a rate limit of _200 requests per second per resource_:
-    * [Run actor](#/reference/actors/run-collection/run-actor)
-    * [Run actor task asynchronously](#/reference/actor-tasks/runs-collection/run-task-asynchronously)
-    * [Run actor task synchronously](#/reference/actor-tasks/runs-collection/run-task-synchronously)
-    * [Metamorph actor run](#/reference/actors/metamorph-run/metamorph-run)
+    * [Run Actor](#/reference/actors/run-collection/run-actor)
+    * [Run Actor task asynchronously](#/reference/actor-tasks/runs-collection/run-task-asynchronously)
+    * [Run Actor task synchronously](#/reference/actor-tasks/runs-collection/run-task-synchronously)
+    * [Metamorph Actor run](#/reference/actors/metamorph-run/metamorph-run)
     * [Push items](#/reference/datasets/item-collection/put-items) to dataset
     * CRUD
       ([add](#/reference/request-queues/request-collection/add-request),