move vocab config and fix snippets

_snippets/data/data-mapping/item-linking-code-node.md

@@ -25,7 +25,7 @@ To control item linking, set `pairedItem` when returning data. For example, to l
 ```
 
 
-### pairedItem usage example
+### `pairedItem` usage example
 
 Take this input data:
 

_snippets/flow-logic/subworkflow-usage.md

@@ -14,10 +14,10 @@ If there are errors in the sub-workflow, the parent workflow can't trigger it.
 /// note | Load data into sub-workflow before building
 This requires the ability to [load data from previous executions](/workflows/executions/debug/), which is available to Pro and Enterprise users.
 
-If you want to load data into your subworkflow to use while building it:
+If you want to load data into your sub-workflow to use while building it:
 
-1. Create the subworkflow and add the **Execute Workflow Trigger**. 
-1. In the subworkflow [settings](/workflows/settings/), set **Save successful production executions** to **Save**. 
+1. Create the sub-workflow and add the **Execute Workflow Trigger**. 
+1. In the sub-workflow [settings](/workflows/settings/), set **Save successful production executions** to **Save**. 
 1. Skip ahead to setting up the parent workflow, and run it.
 1. Follow the steps to [load data from previous executions](/workflows/executions/debug/).
 You'll now have example data pinned in the trigger node, which allows you to work with real data when configuring the rest of the workflow.

_snippets/integrations/builtin/core-nodes/code-node.md

@@ -9,7 +9,7 @@ This page gives usage information about the Code node. For more guidance on codi
 /// 
 
 /// note | Function and Function Item nodes
-The Code node replaces the Function and Function Item nodes from version 0.198.0 onwards. If you're using an older version of n8n, you can still view the [Function node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.function.md){:target=_blank .external-link} and [Function Item node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.functionItem.md){:target=_blank .external-link}.
+The Code node replaces the Function and Function Item nodes from version 0.198.0. If you're using an older version of n8n, you can still view the [Function node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.function.md){:target=_blank .external-link} and [Function Item node documentation](https://github.com/n8n-io/n8n-docs/blob/67935ad2528e2e30d7984ea917e4af2910a096ec/docs/integrations/builtin/core-nodes/n8n-nodes-base.functionItem.md){:target=_blank .external-link}.
 ///
 ## Usage
 

_snippets/integrations/builtin/core-nodes/error-trigger/error-data.md

@@ -29,7 +29,7 @@ All information is always present, except:
 - `execution.url`: requires the execution to be saved in the database. Not present if the error is in the trigger node of the main workflow, as the workflow doesn't execute.
 - `execution.retryOf`: only present when the execution is a retry of a failed execution.
 
-If the error is caused by the trigger node of the main workflow, rather than a later stage, the data sent to the error workflow is different. There is less information in `execution{}` and more in `trigger{}`:
+If the error is caused by the trigger node of the main workflow, rather than a later stage, the data sent to the error workflow is different. There's less information in `execution{}` and more in `trigger{}`:
 
 ```json
 {

_snippets/integrations/builtin/core-nodes/merge/if-merge-branch-execution.md

@@ -7,6 +7,6 @@ The Merge node is triggered by one branch, then goes and executes the other bran
 
 For example, in the screenshot below there's a workflow containing a Edit Fields node, If node, and Merge node. The standard If node behavior is to execute one branch (in the screenshot, this is the **true** output). However, due to the Merge node, both branches execute, despite the If node not sending any data down the **false** branch.
 
-![Screenshot of a simple workflow. The workflow has an Edit Fields node, followed by an If node. It ends with a Merge node.](/_images/integrations/builtin/core-nodes/merge/if-merge-node.png)
+![Screenshot of a workflow. The workflow has an Edit Fields node, followed by an If node. It ends with a Merge node.](/_images/integrations/builtin/core-nodes/merge/if-merge-node.png)
 
 <!-- TODO: remove once v1 is mature -->

_snippets/integrations/creating-nodes/testing.md

@@ -36,7 +36,7 @@ You can test your node as you build it by running it in a local n8n instance.
 
 ### Troubleshooting
 
-- There is no `custom` directory in `~/.n8n` local installation.
+- There's no `custom` directory in `~/.n8n` local installation.
 
 You have to create `custom` directory manually and run `npm init`
 ```shell

styles/Vocab/default/accept.txt → styles/config/vocabularies/default/accept.txt

@@ -62,6 +62,7 @@ Combinator
 Contentful
 ConvertKit
 CPU
+CPython
 CRM
 Cron
 Crypto
@@ -211,6 +212,7 @@ Serverless
 serverless
 Shopify
 shopify
+signup
 Splunk
 Spontit
 Spotify