remove typos workflow & config file

remove typos workflow & config file
create extensive accept.txt that catches known exceptions
add vale turn off in problematic places until better solution is found

Author: TC-MO

.github/styles/config/vocabularies/Docs/accept.txt

@@ -1,21 +1,84 @@
-apify(?=-\w+)
+Apify(?=-\w+)
+@apify\.com
+\bApify\b
 Actor(s)?
+SDK(s)
+[Ss]torages
+Crawlee
+[Aa]utoscaling
+CU
+
 booleans
-Docusaurus
 env
+npm
+serverless
+[Bb]oolean
+node_modules
+[Rr]egex
+[Mm]onorepo
+[Gg]ist
+SDK
+Dockerfile
+Docker's
+
+Docusaurus
 navbar
 nginx
-npm
+
 :::caution
 :::note
 :::info
 :::tip
 :::warning
-Apify
-serverless
-SDK(s)
-[Ss]torages
+
+PDFs
+dataset's
+gif
+Gzip
+
+API's
+APIs
+webhook's
+idempotency
+backoff
+
+Authy
+reCaptcha
+OAuth
+untrusted
+unencrypted
+proxied
+
+LLM
+embedder
+chatbot
+[Ll]angchain
+
+[Kk]eboola
+[Aa]irbyte
+[Qq]drant
+[Pp]inecone
+[Mm]ilvus
+[Zz]illiz
+llama_index
+[Ff]lowise
+
 exploitability
 Whitepaper
 [Cc]ron
-Crawlee
+scalably
+metamorph
+hostname
+IPs
+unscoped
+multistep
+[Aa]utogenerated
+preconfigured
+
+[Ww]ikipedia
+[Zz]apier
+[Tt]rello
+[Pp]refill
+
+
+[Mm]ultiselect

.github/workflows/typos-check.yaml

@@ -11,7 +11,7 @@ mdx = md
 [*.md]
 BasedOnStyles = Vale, Apify, write-good, Microsoft
 # Ignore URLs, HTML/XML tags starting with capital letter, lines containing = sign, http & https URL ending with ] or ) & email addresses
-TokenIgnores = (<\/?[A-Z].+>), ([^\n]+=[^\n]*), (http[^\n]+\)), (https[^\n]+\)), ([^\n]+@[^\n]+\.[^\n]), (http[^\n]+\]), (https[^\n]+\])
+TokenIgnores = (<\/?[A-Z].+>), ([^\n]+=[^\n]*), (\[[^\]]+\]\([^\)]+\)), ([^\n]+@[^\n]+\.[^\n]), ({[^}]*}), (`[^`]*`), (`\w+`)
 Vale.Spelling = YES
 
 

.vale.ini

@@ -5,7 +5,7 @@ slug: /actors/development/actor-definition/actor-json
 sidebar_position: 1
 ---
 
-**Learn how to write the main Actor config in the `.actor/actor.json` file.**
+**Learn how to write the main Actor configuration in the `.actor/actor.json` file.**
 
 ---
 

_typos.toml

@@ -34,9 +34,9 @@ To make an input field secret, you need to add a `"isSecret": true` setting to t
 ```
 
 The editor for this input field will then turn into a secret input, and when you edit the field value, it will be stored encrypted.
-
+<!-- vale off -->
 <img src={require("./images/secret-input-editor.png").default} alt="Secret input editor" style={{ width: '100%', maxWidth: '822px' }}/>
-
+<!-- vale on -->
 :::note Type restriction
 
 This is only available for `string` inputs, and the editor type is limited to `textfield` or `textarea`.

sources/platform/actors/development/actor_definition/actor_json.md

@@ -18,7 +18,7 @@ The Actor input schema serves three main purposes:
 - It simplifies invoking your Actors from external systems by generating calling code and connectors for integrations.
 
 To define an input schema for an Actor, set `input` field in the `.actor/actor.json` file to an input schema object (described below), or path to a JSON file containing the input schema object.
-For backwards compatibility, if the `input` field is omitted, the system looks for an `INPUT_SCHEMA.json` file either in the `.actor` directory or the Actor's top-level directory—but note that this functionality is deprececated and might be removed in the future. The maximum allowed size for the input schema file is 500 kB.
+For backwards compatibility, if the `input` field is omitted, the system looks for an `INPUT_SCHEMA.json` file either in the `.actor` directory or the Actor's top-level directory—but note that this functionality is deprecated and might be removed in the future. The maximum allowed size for the input schema file is 500 kB.
 
 When you provide an input schema, the system will validate the input data passed to the Actor on start (via the API or Apify Console) against the specified schema to ensure compliance before starting the Actor.
 If the input object doesn't conform the schema, the caller receives an error and the Actor is not started.
@@ -343,7 +343,7 @@ The object where the proxy configuration is stored has the following structure:
 }
 ```
 
-Example of a blackbox object:
+Example of a black box object:
 
 ```json
 {

sources/platform/actors/development/actor_definition/input_schema/secret_input.md

@@ -11,7 +11,7 @@ slug: /actors/development/builds-and-runs/builds
 
 ## Understand Actor builds
 
-Before an Actor can be run, it needs to be built. The build process creates a snapshot of a specific version of the Actor's settings, including its [source code](../actor_definition/source_code.md) and [environment variables](../programming_interface/environment_variables.md). This snapshot is then used to create a Docker image containing everything the Actor needs for its run, such as NPM packages, web browsers, etc.
+Before an Actor can be run, it needs to be built. The build process creates a snapshot of a specific version of the Actor's settings, including its [source code](../actor_definition/source_code.md) and [environment variables](../programming_interface/environment_variables.md). This snapshot is then used to create a Docker image containing everything the Actor needs for its run, such as `npm` packages, web browsers, etc.
 
 ### Build numbers
 

sources/platform/actors/development/actor_definition/input_schema/specification.md

@@ -18,7 +18,7 @@ Long-running [Actor](../../index.mdx) jobs may need to migrate between servers.
 To prevent data loss, long-running Actors should:
 
 - Periodically save (persist) their state.
-- Listem for [migration events](/sdk/js/api/apify/class/PlatformEventManager)
+- Listen for [migration events](/sdk/js/api/apify/class/PlatformEventManager)
 - Check for persisted state when starting, allowing them to resume from where they left off.
 
 For short-running Actors, the risk of restarts and the cost of repeated runs are low, so you can typically ignore state persistence.

sources/platform/actors/development/builds_and_runs/builds.md

@@ -30,7 +30,7 @@ To set up automated builds and tests for your Actors you need to:
     ![Apify token in app](./images/ci-token.png)
 
 1. Add your Apify token to GitHub secrets
-   1. Go to your repo > Settings > Secrets > New repository secret
+   1. Go to your repository > Settings > Secrets > New repository secret
    1. Name the secret & paste in your token
 1. Add the Builds Actor API endpoint URL to GitHub secrets
    1. Use this format:
@@ -43,7 +43,7 @@ To set up automated builds and tests for your Actors you need to:
 
    1. Name the secret
 1. Create GitHub Actions workflow files:
-   1. In your repo, create the `.github/workflows` directory
+   1. In your repository, create the `.github/workflows` directory
    2. Add `latest.yml` and `beta.yml` files with the following content
 
     <Tabs groupId="main">