diff --git a/content/actions/learn-github-actions/contexts.md b/content/actions/learn-github-actions/contexts.md
index 6fd4f39039..cc3aa6d5d9 100644
--- a/content/actions/learn-github-actions/contexts.md
+++ b/content/actions/learn-github-actions/contexts.md
@@ -21,32 +21,39 @@ miniTocMaxHeadingLevel: 3
 
 ## About contexts
 
-{% data reusables.github-actions.context-injection-warning %}
+Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Each context is an object that contains properties, which can be strings or other objects.
 
-Contexts are a way to access information about workflow runs, runner environments, jobs, and steps. Contexts use the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
+{% data reusables.actions.context-contents %} For example, the `matrix` context is only populated for jobs in a [build matrix](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymatrix).
+
+You can access contexts using the expression syntax. For more information, see "[Expressions](/actions/learn-github-actions/expressions)."
 
 {% raw %}
 `${{ <context> }}`
 {% endraw %}
 
+{% data reusables.github-actions.context-injection-warning %}
+
 | Context name | Type | Description |
 |---------------|------|-------------|
 | `github` | `object` | Information about the workflow run. For more information, see [`github` context](#github-context). |
 | `env` | `object` | Contains environment variables set in a workflow, job, or step. For more information, see [`env` context](#env-context). |
-| `job` | `object` | Information about the currently executing job. For more information, see [`job` context](#job-context). |
-| `steps` | `object` | Information about the steps that have been run in this job. For more information, see [`steps` context](#steps-context). |
+| `job` | `object` | Information about the currently running job. For more information, see [`job` context](#job-context). |
+| `steps` | `object` | Information about the steps that have been run in the current job. For more information, see [`steps` context](#steps-context). |
 | `runner` | `object` | Information about the runner that is running the current job. For more information, see [`runner` context](#runner-context). |
-| `secrets` | `object` | Enables access to secrets. For more information about secrets, see "[Creating and using encrypted secrets](/actions/automating-your-workflow-with-github-actions/creating-and-using-encrypted-secrets)." |
-| `strategy` | `object` | Enables access to the configured strategy parameters and information about the current job. Strategy parameters include `fail-fast`, `job-index`, `job-total`, and `max-parallel`. |
-| `matrix` | `object` | Enables access to the matrix parameters you configured for the current job. For example, if you configure a matrix build with the `os` and `node` versions, the `matrix` context object includes the `os` and `node` versions of the current job. |
-| `needs` | `object` | Enables access to the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}| `inputs` | `object` | Enables access to the inputs of reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
+| `secrets` | `object` | Contains the names and values of secrets that are available to a workflow run. For more information, see [`secrets` context](#secrets-context). |
+| `strategy` | `object` | Information about the matrix execution strategy for the current job. For more information, see [`strategy` context](#strategy-context). |
+| `matrix` | `object` | Contains the matrix properties defined in the workflow that apply to the current job. For more information, see [`matrix` context](#matrix-context). |
+| `needs` | `object` | Contains the outputs of all jobs that are defined as a dependency of the current job. For more information, see [`needs` context](#needs-context). |
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
+| `inputs` | `object` | Contains the inputs of a reusable workflow. For more information, see [`inputs` context](#inputs-context). |{% endif %}
+
+As part of an expression, you can access context information using one of two syntaxes.
 
-As part of an expression, you may access context information using one of two syntaxes.
 - Index syntax: `github['sha']`
 - Property dereference syntax: `github.sha`
 
 In order to use property dereference syntax, the property name must:
+
 - start with `a-Z` or `_`.
 - be followed by `a-Z` `0-9` `-` or `_`.
 
@@ -54,162 +61,7 @@ In order to use property dereference syntax, the property name must:
 
 {% data reusables.github-actions.using-context-or-environment-variables %}
 
-### `github` context
-
-The `github` context contains information about the workflow run and the event that triggered the run. You can read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
-
-{% data reusables.github-actions.github-context-warning %}
-{% data reusables.github-actions.context-injection-warning %}
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `github` | `object` | The top-level context available during any job or step in a workflow. |
-| `github.action` | `string` | The name of the action currently running. {% data variables.product.prodname_dotcom %} removes special characters or uses the name `__run` when the current step runs a script.  If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it.  For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
-| `github.action_path` | `string` | The path where your action is located. You can use this path to easily access files located in the same repository as your action. This attribute is only supported in composite actions. |
-| `github.actor` | `string` | The login of the user that initiated the workflow run. |
-| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
-| `github.event` | `object` | The full event webhook payload. For more information, see "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." You can access individual properties of the event using this context. |
-| `github.event_name` | `string` | The name of the event that triggered the workflow run. |
-| `github.event_path` | `string` | The path to the full event webhook payload on the runner. |
-| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
-| `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`. |
-{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
-| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
-| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
-{%- endif %}
-| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
-| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
-| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
-| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
-| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
-| `github.server_url` | `string` | Returns the URL of the GitHub server. For example: `https://github.com`. |
-| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
-| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Authenticating with the GITHUB_TOKEN](/actions/automating-your-workflow-with-github-actions/authenticating-with-the-github_token)." |
-| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
-| `github.workspace` | `string` | The default working directory for steps and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
-
-### `env` context
-
-The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
-
-The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a **step** except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
-
-If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `env.<env_name>` | `string` | The value of a specific environment variable. |
-
-### `job` context
-
-The `job` context contains information about the currently running job.
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. |
-| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
-| `job.container.id` | `string` | The id of the container. |
-| `job.container.network` | `string` | The id of the container network. The runner creates the network used by all containers in a job. |
-| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
-| `job.services.<service id>.id` | `string` | The id of the service container. |
-| `job.services.<service id>.network` | `string` | The id of the service container network. The runner creates the network used by all containers in a job. |
-| `job.services.<service id>.ports` | `object` | The exposed ports of the service container. |
-| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
-
-### `steps` context
-
-The `steps` context contains information about the steps in the current job that have already run.
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. |
-| `steps.<step id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
-| `steps.<step id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
-| `steps.<step id>.outputs.<output name>` | `string` | The value of a specific output. |
-
-### `runner` context
-
-The `runner` context contains information about the runner that is executing the current job.
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
-| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
-| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
-| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
-| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
-
-### `needs` context
-
-The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idneeds)."
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `needs.<job id>` | `object` | A single job that the current job depends on. |
-| `needs.<job id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
-| `needs.<job id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
-| `needs.<job id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
-
-{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
-### `inputs` context
-
-The `inputs` context contains information about the inputs of reusable workflow. The inputs are defined in [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events). These inputs are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow.
-
-For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)".
-
-| Property name | Type | Description |
-|---------------|------|-------------|
-| `inputs` | `object` | This context is only available when it is [a reusable workflow](/actions/learn-github-actions/reusing-workflows). |
-| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
-{% endif %}
-
-#### Example printing context information to the log file
-
-To inspect the information that is accessible in each context, you can use this workflow file example.
-
-{% data reusables.github-actions.github-context-warning %}
-
-**.github/workflows/main.yml**
-{% raw %}
-```yaml
-on: push
-
-jobs:
-  one:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Dump GitHub context
-        env:
-          GITHUB_CONTEXT: ${{ toJSON(github) }}
-        run: echo "$GITHUB_CONTEXT"
-      - name: Dump job context
-        env:
-          JOB_CONTEXT: ${{ toJSON(job) }}
-        run: echo "$JOB_CONTEXT"
-      - name: Dump steps context
-        env:
-          STEPS_CONTEXT: ${{ toJSON(steps) }}
-        run: echo "$STEPS_CONTEXT"
-      - name: Dump runner context
-        env:
-          RUNNER_CONTEXT: ${{ toJSON(runner) }}
-        run: echo "$RUNNER_CONTEXT"
-      - name: Dump strategy context
-        env:
-          STRATEGY_CONTEXT: ${{ toJSON(strategy) }}
-        run: echo "$STRATEGY_CONTEXT"
-      - name: Dump matrix context
-        env:
-          MATRIX_CONTEXT: ${{ toJSON(matrix) }}
-        run: echo "$MATRIX_CONTEXT"
-```
-{% endraw %}
-
-## Context availability
+### Context availability
 
 Different contexts are available throughout a workflow run. For example, the `secrets` context may only be used at certain places within a job.
 
@@ -219,7 +71,7 @@ The following table indicates where each context and special function can be use
 
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
 
-| Path | Context | Special functions |
+| Workflow key | Context | Special functions |
 | ---- | ------- | ----------------- |
 | <code>concurrency</code> | <code>github, inputs</code> | |
 | <code>env</code> | <code>github, secrets, inputs</code> | |
@@ -284,4 +136,639 @@ The following table indicates where each context and special function can be use
 | <code>jobs.&lt;job_id&gt;.steps.working-directory</code> | <code>github, needs, strategy, matrix, job, runner, env, secrets, steps</code> | <code>hashFiles</code> |
 | <code>jobs.&lt;job_id&gt;.strategy</code> | <code>github, needs</code> | |
 | <code>jobs.&lt;job_id&gt;.timeout-minutes</code> | <code>github, needs, strategy, matrix</code> | |
-{% endif %}
\ No newline at end of file
+{% endif %}
+
+### Example: printing context information to the log
+
+You can print the contents of contexts to the log for debugging. The [`toJSON` function](/actions/learn-github-actions/expressions#tojson) is required to pretty-print JSON objects to the log.
+
+{% data reusables.github-actions.github-context-warning %}
+
+{% raw %}
+```yaml{:copy}
+name: Context testing
+on: push
+
+jobs:
+  dump_contexts_to_log:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Dump GitHub context
+        id: github_context_step
+        run: echo '${{ toJSON(github) }}'
+      - name: Dump job context
+        run: echo '${{ toJSON(job) }}'
+      - name: Dump steps context
+        run: echo '${{ toJSON(steps) }}'
+      - name: Dump runner context
+        run: echo '${{ toJSON(runner) }}'
+      - name: Dump strategy context
+        run: echo '${{ toJSON(strategy) }}'
+      - name: Dump matrix context
+        run: echo '${{ toJSON(matrix) }}'
+```
+{% endraw %}
+
+## `github` context
+
+The `github` context contains information about the workflow run and the event that triggered the run. You can also read most of the `github` context data in environment variables. For more information about environment variables, see "[Using environment variables](/actions/automating-your-workflow-with-github-actions/using-environment-variables)."
+
+{% data reusables.github-actions.github-context-warning %}
+{% data reusables.github-actions.context-injection-warning %}
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `github` | `object` | The top-level context available during any job or step in a workflow. This object contains all the properties listed below. |
+| `github.action` | `string` | The name of the action currently running, or the [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) of a step. {% data variables.product.prodname_dotcom %} removes special characters, and uses the name `__run` when the current step runs a script without an `id`. If you use the same action more than once in the same job, the name will include a suffix with the sequence number with underscore before it. For example, the first script you run will have the name `__run`, and the second script will be named `__run_2`. Similarly, the second invocation of `actions/checkout` will be `actionscheckout2`. |
+| `github.action_path` | `string` | The path where an action is located. This property is only supported in composite actions. You can use this path to access files located in the same repository as the action. |
+| `github.action_ref` | `string` | For a step executing an action, this is the ref of the action being executed. For example, `v2`.
+| `github.action_repository` | `string` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`.
+| `github.actor` | `string` | The username of the user that initiated the workflow run. |
+| `github.api_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} REST API. |
+| `github.base_ref` | `string` | The `base_ref` or target branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
+| `github.env` | `string` | Path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#setting-an-environment-variable)."
+| `github.event` | `object` | The full event webhook payload. You can access individual properties of the event using this context. This object is identical to the webhook payload of the event that triggered the workflow run, and is different for each event. The webhooks for each {% data variables.product.prodname_actions %} event is linked in "[Events that trigger workflows](/articles/events-that-trigger-workflows/)." For example, for a workflow run triggered by the [`push` event](http://localhost:4000/en/actions/learn-github-actions/events-that-trigger-workflows#push), this object contains the contents of the [push webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push). |
+| `github.event_name` | `string` | The name of the event that triggered the workflow run. |
+| `github.event_path` | `string` | The path to the file on the runner that contains the full event webhook payload. |
+| `github.graphql_url` | `string` | The URL of the {% data variables.product.prodname_dotcom %} GraphQL API. |
+| `github.head_ref` | `string` | The `head_ref` or source branch of the pull request in a workflow run. This property is only available when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. |
+| `github.job` | `string` | The [`job_id`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
+| `github.ref` | `string` | The branch or tag ref that triggered the workflow run. For branches this is the format  `refs/heads/<branch_name>`, and for tags it is `refs/tags/<tag_name>`. |
+{%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
+| `github.ref_name` | `string` | {% data reusables.actions.ref_name-description %} |
+| `github.ref_protected` | `string` | {% data reusables.actions.ref_protected-description %} |
+| `github.ref_type` | `string` | {% data reusables.actions.ref_type-description %} |
+{%- endif %}
+| `github.path` | `string` | Path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and is a different file for each step in a job. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-commands-for-github-actions#adding-a-system-path)." |
+| `github.repository` | `string` | The owner and repository name. For example, `Codertocat/Hello-World`. |
+| `github.repository_owner` | `string` | The repository owner's name. For example, `Codertocat`. |
+| `github.repositoryUrl` | `string` | The Git URL to the repository. For example, `git://github.com/codertocat/hello-world.git`. |
+| `github.retention_days` | `string` | The number of days that workflow run logs and artifacts are kept. |
+| `github.run_id` | `string` | {% data reusables.github-actions.run_id_description %} |
+| `github.run_number` | `string` | {% data reusables.github-actions.run_number_description %} |
+| `github.run_attempt` | `string` | A unique number for each attempt of a particular workflow run in a repository. This number begins at 1 for the workflow run's first attempt, and increments with each re-run. |
+| `github.server_url` | `string` | The URL of the GitHub server. For example: `https://github.com`. |
+| `github.sha` | `string` | The commit SHA that triggered the workflow run. |
+| `github.token` | `string` | A token to authenticate on behalf of the GitHub App installed on your repository. This is functionally equivalent to the `GITHUB_TOKEN` secret. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." |
+| `github.workflow` | `string` | The name of the workflow. If the workflow file doesn't specify a `name`, the value of this property is the full path of the workflow file in the repository. |
+| `github.workspace` | `string` | The default working directory on the runner for steps, and the default location of your repository when using the [`checkout`](https://github.com/actions/checkout) action. |
+
+### Example contents of the `github` context
+
+The following example context is from a workflow run triggered by the `push` event. The `event` object in this example has been truncated because it is identical to the contents of the [`push` webhook payload](/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#push).
+
+{% data reusables.actions.context-example-note %}
+
+```json
+{
+  "token": "***",
+  "job": "dump_contexts_to_log",
+  "ref": "refs/heads/my_branch",
+  "sha": "c27d339ee6075c1f744c5d4b200f7901aad2c369",
+  "repository": "octocat/hello-world",
+  "repository_owner": "octocat",
+  "repositoryUrl": "git://github.com/octocat/hello-world.git",
+  "run_id": "1536140711",
+  "run_number": "314",
+  "retention_days": "90",
+  "run_attempt": "1",
+  "actor": "octocat",
+  "workflow": "Context testing",
+  "head_ref": "",
+  "base_ref": "",
+  "event_name": "push",
+  "event": {
+    ...
+  },
+  "server_url": "https://github.com",
+  "api_url": "https://api.github.com",
+  "graphql_url": "https://api.github.com/graphql",
+  "ref_name": "my_branch",
+  "ref_protected": false,
+  "ref_type": "branch",
+  "secret_source": "Actions",
+  "workspace": "/home/runner/work/hello-world/hello-world",
+  "action": "github_step",
+  "event_path": "/home/runner/work/_temp/_github_workflow/event.json",
+  "action_repository": "",
+  "action_ref": "",
+  "path": "/home/runner/work/_temp/_runner_file_commands/add_path_b037e7b5-1c88-48e2-bf78-eaaab5e02602",
+  "env": "/home/runner/work/_temp/_runner_file_commands/set_env_b037e7b5-1c88-48e2-bf78-eaaab5e02602"
+}
+```
+
+### Example usage of the `github` context
+
+This example workflow uses the `github.event_name` context to run a job only if the workflow run was triggered by the `pull_request` event.
+
+```yaml{:copy}
+name: Run CI
+on: [push, pull_request]
+
+jobs:
+  normal_ci:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Run normal CI
+        run: ./run-tests
+
+  pull_request_ci:
+    runs-on: ubuntu-latest
+    if: {% raw %}${{ github.event_name == 'pull_request' }}{% endraw %}
+    steps:
+      - uses: actions/checkout@v2
+      - name: Run PR CI
+        run: ./run-additional-pr-ci
+```
+
+## `env` context
+
+The `env` context contains environment variables that have been set in a workflow, job, or step. For more information about setting environment variables in your workflow, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env)."
+
+The `env` context syntax allows you to use the value of an environment variable in your workflow file. You can use the `env` context in the value of any key in a step except for the `id` and `uses` keys. For more information on the step syntax, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idsteps)."
+
+If you want to use the value of an environment variable inside a runner, use the runner operating system's normal method for reading environment variables.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `env` | `object` | This context changes for each step in a job. You can access this context from any step in a job. This object contains the properties listed below. |
+| `env.<env_name>` | `string` | The value of a specific environment variable. |
+
+### Example contents of the `env` context
+
+The contents of the `env` context is a mapping of environment variable names to their values. The context's contents can change depending on where it is used in the workflow run.
+
+```json
+{
+  "first_name": "Mona",
+  "super_duper_var": "totally_awesome"
+}
+```
+
+### Example usage of the `env` context
+
+This example workflow shows how the `env` context can be configured at the workflow, job, and step levels, as well as using the context in steps.
+
+{% data reusables.repositories.actions-env-var-note %}
+
+{% raw %}
+```yaml{:copy}
+name: Hi Mascot
+on: push
+env:
+  mascot: Mona
+  super_duper_var: totally_awesome
+
+jobs:
+  windows_job:
+    runs-on: windows-latest
+    steps:
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Mona
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Octocat
+        env:
+          mascot: Octocat
+  linux_job:
+    runs-on: ubuntu-latest
+    env:
+      mascot: Tux
+    steps:
+      - run: echo 'Hi ${{ env.mascot }}'  # Hi Tux
+```
+{% endraw %}
+
+## `job` context
+
+The `job` context contains information about the currently running job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `job` | `object` | This context changes for each job in a workflow run. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `job.container` | `object` | Information about the job's container. For more information about containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idcontainer)." |
+| `job.container.id` | `string` | The ID of the container. |
+| `job.container.network` | `string` | The ID of the container network. The runner creates the network used by all containers in a job. |
+| `job.services` | `object` | The service containers created for a job. For more information about service containers, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/articles/workflow-syntax-for-github-actions#jobsjob_idservices)." |
+| `job.services.<service_id>.id` | `string` | The ID of the service container. |
+| `job.services.<service_id>.network` | `string` | The ID of the service container network. The runner creates the network used by all containers in a job. |
+| `job.services.<service_id>.ports` | `object` | The exposed ports of the service container. |
+| `job.status` | `string` | The current status of the job. Possible values are `success`, `failure`, or `cancelled`. |
+
+### Example contents of the `job` context
+
+This example `job` context uses a PostgreSQL service container with mapped ports. If there are no containers or service containers used in a job, the `job` context only contains the `status` property.
+
+```json
+{
+  "status": "success",
+  "container": {
+    "network": "github_network_53269bd575974817b43f4733536b200c"
+  },
+  "services": {
+    "postgres": {
+      "id": "60972d9aa486605e66b0dad4abb638dc3d9116f566579e418166eedb8abb9105",
+      "ports": {
+        "5432": "49153"
+      },
+      "network": "github_network_53269bd575974817b43f4733536b200c"
+    }
+  }
+}
+```
+
+### Example usage of the `job` context
+
+This example workflow configures a PostgreSQL service container, and automatically maps port 5432 in the service container to a randomly chosen available port on the host. The `job` context is used to access the number of the port that was assigned on the host.
+
+{% raw %}
+```yaml{:copy}
+name: PostgreSQL Service Example
+on: push
+jobs:
+  postgres-job:
+    runs-on: ubuntu-latest
+    services:
+      postgres:
+        image: postgres
+        env:
+          POSTGRES_PASSWORD: postgres
+        options: --health-cmd pg_isready --health-interval 10s --health-timeout 5s --health-retries 5
+        ports:
+          # Maps TCP port 5432 in the service container to a randomly chosen available port on the host.
+          - 5432
+
+    steps:
+      - uses: actions/checkout@v2
+      - run: pg_isready -h localhost -p ${{ job.services.postgres.ports[5432] }}
+      - run: ./run-tests
+```
+{% endraw %}
+
+## `steps` context
+
+The `steps` context contains information about the steps in the current job that have an [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) specified and have already run.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `steps` | `object` | This context changes for each step in a job. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `steps.<step_id>.outputs` | `object` | The set of outputs defined for the step. For more information, see "[Metadata syntax for {% data variables.product.prodname_actions %}](/articles/metadata-syntax-for-github-actions#outputs)." |
+| `steps.<step_id>.conclusion` | `string` | The result of a completed step after [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
+| `steps.<step_id>.outcome` | `string` | The result of a completed step before [`continue-on-error`](/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepscontinue-on-error) is applied. Possible values are `success`, `failure`, `cancelled`, or `skipped`. When a `continue-on-error` step fails, the `outcome` is `failure`, but the final `conclusion` is `success`. |
+| `steps.<step_id>.outputs.<output_name>` | `string` | The value of a specific output. |
+
+### Example contents of the `steps` context
+
+This example `steps` context shows two previous steps that had an [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) specified. The first step had the `id` named `checkout`, the second `generate_number`. The `generate_number` step had an output named `random_number`.
+
+```yaml
+{
+  "checkout": {
+    "outputs": {},
+    "outcome": "success",
+    "conclusion": "success"
+  },
+  "generate_number": {
+    "outputs": {
+      "random_number": "1"
+    },
+    "outcome": "success",
+    "conclusion": "success"
+  }
+}
+```
+
+### Example usage of the `steps` context
+
+This example workflow generates a random number as an output in one step, and a later step uses the `steps` context to read the value of that output.
+
+{% raw %}
+```yaml{:copy}
+name: Generate random failure
+on: push
+jobs:
+  randomly-failing-job:
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        uses: actions/checkout@v2
+      - name: Generate 0 or 1
+        id: generate_number
+        run:  echo "::set-output name=random_number::$(($RANDOM % 2))"
+      - name: Pass or fail
+        run: |
+          if [[ ${{ steps.generate_number.outputs.random_number }} == 0 ]]; then exit 0; else exit 1; fi
+```
+{% endraw %}
+
+## `runner` context
+
+The `runner` context contains information about the runner that is executing the current job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `runner` | `object` | This context changes for each job in a workflow run. This object contains all the properties listed below. |
+| `runner.name` | `string` | {% data reusables.actions.runner-name-description %} |
+| `runner.os` | `string` | {% data reusables.actions.runner-os-description %} |{% if actions-runner-arch-envvars %}
+| `runner.arch` | `string` | {% data reusables.actions.runner-arch-description %} |{% endif %}
+| `runner.temp` | `string` | {% data reusables.actions.runner-temp-directory-description %} |
+| `runner.tool_cache` | `string` | {% ifversion ghae %}{% data reusables.actions.self-hosted-runners-software %} {% else %} {% data reusables.actions.runner-tool-cache-description %} {% endif %}|
+{%- comment %}
+The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility.
+| `runner.workspace` | `string` | |
+{%- endcomment %}
+
+### Example contents of the `runner` context
+
+The following example context is from a Linux {% data variables.product.prodname_dotcom %}-hosted runner.
+
+```yaml
+{
+  "os": "Linux",
+  "arch": "X64",
+  "name": "GitHub Actions 2",
+  "tool_cache": "/opt/hostedtoolcache",
+  "temp": "/home/runner/work/_temp"
+  {%- comment %}
+  # The `runner.workspace` property is purposefully not documented. It is an early Actions property that now isn't relevant for users, compared to `github.workspace`. It is kept around for compatibility.
+  "workspace": "/home/runner/work/hello-world"
+  {%- endcomment %}
+}
+```
+
+### Example usage of the `runner` context
+
+This example workflow uses the `runner` context to set the path to the temporary directory to write logs, and if the workflow fails, it uploads those logs as artifact.
+
+{% raw %}
+```yaml{:copy}
+name: Build
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build with logs
+        run: |
+          mkdir ${{ runner.temp }}/build_logs
+          ./build.sh --log-path ${{ runner.temp }}/build_logs
+      - name: Upload logs on fail
+        if: ${{ failure() }}
+        uses: actions/upload-artifact@v2
+        with:
+          name: Build failure logs
+          path: ${{ runner.temp }}/build_logs
+```
+{% endraw %}
+
+## `secrets` context
+
+The `secrets` context contains the names and values of secrets that are available to a workflow run. The `secrets` context is not available for composite actions. For more information about secrets, see "[Encrypted secrets](/actions/security-guides/encrypted-secrets)."
+
+`GITHUB_TOKEN` is a secret that is automatically created for every workflow run, and is always included in the `secrets` context. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)."
+
+{% data reusables.github-actions.secrets-redaction-warning %}
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `secrets` | `object` | This context is the same for each job in a workflow run. You can access this context from any step in a job. This object contains all the properties listed below. |
+| `secrets.GITHUB_TOKEN` | `string` | Automatically created token for each workflow run. For more information, see "[Automatic token authentication](/actions/security-guides/automatic-token-authentication)." |
+| `secrets.<secret_name>` | `string` | The value of a specific secret. |
+
+### Example contents of the `secrets` context
+
+The following example contents of the `secrets` context shows the automatic `GITHUB_TOKEN`, as well as two other secrets available to the workflow run.
+
+```yaml
+{
+  "github_token": "***",
+  "NPM_TOKEN": "***",
+  "SUPERSECRET": "***"
+}
+```
+
+### Example usage of the `secrets` context
+
+{% data reusables.github-actions.github_token-input-example %}
+
+## `strategy` context
+
+For workflows with a build matrix, the `strategy` context contains information about the matrix execution strategy for the current job.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `strategy` | `object` | This context changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
+| `strategy.fail-fast` | `string` | When `true`, all in-progress jobs are canceled if any job in a build matrix fails. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategyfail-fast)." |
+| `strategy.job-index` | `string` | The index of the current job in the build matrix. **Note:** This number is a zero-based number. The first job's index in the build matrix is `0`. |
+| `strategy.job-total` | `string` | The total number of jobs in the build matrix. **Note:** This number **is not** a zero-based number. For example, for a build matrix with four jobs, the value of `job-total` is `4`. |
+| `strategy.max-parallel` | `string` | The maximum number of jobs that can run simultaneously when using a `matrix` job strategy. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstrategymax-parallel)." |
+
+### Example contents of the `strategy` context
+
+The following example contents of the `strategy` context is from a build matrix with four jobs, and is taken from the final job. Note the difference between the zero-based `job-index` number, and `job-total` which is not zero-based.
+
+```yaml
+{
+  "fail-fast": true,
+  "job-index": 3,
+  "job-total": 4,
+  "max-parallel": 4
+}
+```
+
+### Example usage of the `strategy` context
+
+This example workflow uses the `strategy.job-index` property to set a unique name for a log file for each job in a build matrix.
+
+{% raw %}
+```yaml{:copy}
+name: Test matrix
+on: push
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        test-group: [1, 2]
+        node: [14, 16]
+    steps:
+      - uses: actions/checkout@v2
+      - run: npm test > test-job-${{ strategy.job-index }}.txt
+      - name: Upload logs
+        uses: actions/upload-artifact@v2
+        with:
+          name: Build log for job ${{ strategy.job-index }}
+          path: test-job-${{ strategy.job-index }}.txt
+```
+{% endraw %}
+
+## `matrix` context
+
+For workflows with a build matrix, the `matrix` context contains the matrix properties defined in the workflow file that apply to the current job. For example, if you configure a build matrix with the `os` and `node` keys, the `matrix` context object includes the `os` and `node` properties with the values that are being used for the current job.
+
+There are no standard properties in the `matrix` context, only those which are defined in the workflow file.
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `matrix` | `object` | This context is only available for jobs in a build matrix, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains the properties listed below. |
+| `matrix.<property_name>` | `string` | The value of a matrix property. |
+
+### Example contents of the `matrix` context
+
+The following example contents of the `matrix` context is from a job in a build matrix that has the `os` and `node` matrix properties defined in the workflow. The job is executing the matrix combination of an `ubuntu-latest` OS and Node.js version `16`.
+
+```yaml
+{
+  "os": "ubuntu-latest",
+  "node": 16
+}
+```
+
+### Example usage of the `matrix` context
+
+This example workflow creates a build matrix with `os` and `node` keys. It uses the `matrix.os` property to set the runner type for each job, and uses the `matrix.node` property to set the Node.js version for each job.
+
+{% raw %}
+```yaml{:copy}
+name: Test matrix
+on: push
+
+jobs:
+  build:
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        os: [ubuntu-latest, windows-latest]
+        node: [14, 16]
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: ${{ matrix.node }}
+      - name: Install dependencies
+        run: npm ci
+      - name: Run tests
+        run: npm test
+```
+{% endraw %}
+
+## `needs` context
+
+The `needs` context contains outputs from all jobs that are defined as a dependency of the current job. For more information on defining job dependencies, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idneeds)."
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `needs` | `object` | This context is only populated for workflow runs that have dependent jobs, and changes for each job in a workflow run. You can access this context from any job or step in a workflow. This object contains all the properties listed below. |
+| `needs.<job_id>` | `object` | A single job that the current job depends on. |
+| `needs.<job_id>.outputs` | `object` | The set of outputs of a job that the current job depends on. |
+| `needs.<job_id>.outputs.<output name>` | `string` | The value of a specific output for a job that the current job depends on. |
+| `needs.<job_id>.result` | `string` | The result of a job that the current job depends on. Possible values are `success`, `failure`, `cancelled`, or `skipped`. |
+
+### Example contents of the `needs` context
+
+The following example contents of the `needs` context shows information for two jobs that the current job depends on.
+
+```yaml
+{
+  "build": {
+    "result": "success",
+    "outputs": {
+      "build_id": "ABC123"
+    }
+  },
+  "deploy": {
+    "result": "failure",
+    "outputs": {}
+  }
+}
+```
+
+### Example usage of the `needs` context
+
+This example workflow has three jobs: a `build` job that does a build, a `deploy` job that requires the `build` job, and a `debug` job that requires both the `build` and `deploy` jobs and runs only if there is a failure in the workflow. The `deploy` job also uses the `needs` context to access an output from the `build` job.
+
+{% raw %}
+```yaml{:copy}
+name: Build and deploy
+on: push
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    outputs:
+      build_id: ${{ steps.build_step.outputs.build_id }}
+    steps:
+      - uses: actions/checkout@v2
+      - name: Build
+        id: build_step
+        run: |
+          ./build
+          echo "::set-output name=build_id::$BUILD_ID" 
+  deploy:
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - run: ./deploy --build ${{ needs.build.outputs.build_id }}
+  debug:
+    needs: [build, deploy]
+    runs-on: ubuntu-latest
+    if: ${{ failure() }}
+    steps:
+      - uses: actions/checkout@v2
+      - run: ./debug
+```
+{% endraw %}
+
+{% ifversion fpt or ghec or ghes > 3.3 or ghae-issue-4757 %}
+## `inputs` context
+
+The `inputs` context contains input properties passed to a reusable workflow. The input names and types are defined in the [`workflow_call` event configuration](/actions/learn-github-actions/events-that-trigger-workflows#workflow-reuse-events) of a reusable workflow, and the input values are passed from [`jobs.<job_id>.with`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idwith) in an external workflow that calls the reusable workflow.
+
+There are no standard properties in the `inputs` context, only those which are defined in the reusable workflow file.
+
+For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)".
+
+| Property name | Type | Description |
+|---------------|------|-------------|
+| `inputs` | `object` | This context is only available in a [reusable workflow](/actions/learn-github-actions/reusing-workflows). You can access this context from any job or step in a workflow. This object contains the properties listed below. |
+| `inputs.<name>` | `string` or `number` or `boolean` | Each input value passed from an external workflow. |
+
+### Example contents of the `inputs` context
+
+The following example contents of the `inputs` context is from a job in a reusable workflow that has defined the `build_id` and `deploy_target` inputs.
+
+```yaml
+{
+  "build_id": 123456768,
+  "deploy_target": "deployment_sys_1a"
+}
+```
+
+### Example usage of the `inputs` context
+
+This example reusable workflow uses the `inputs` context to get the values of the `build_id` and `deploy_target` inputs that were passed to the reusable workflow from the caller workflow.
+
+{% raw %}
+```yaml{:copy}
+name: Reusable deploy workflow
+on:
+  workflow_call:
+    inputs:
+      build_id:
+        required: true
+        type: number
+      deploy_target:
+        required: true
+        type: string
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Deploy build to target
+        run: deploy --build ${{ inputs.build_id }} --target ${{ inputs.deploy_target }}
+```
+{% endraw %}
+{% endif %}
diff --git a/content/actions/security-guides/automatic-token-authentication.md b/content/actions/security-guides/automatic-token-authentication.md
index 40d3af358b..5ddb5ccb0e 100644
--- a/content/actions/security-guides/automatic-token-authentication.md
+++ b/content/actions/security-guides/automatic-token-authentication.md
@@ -43,26 +43,7 @@ You can use the `GITHUB_TOKEN` by using the standard syntax for referencing secr
 
 ### Example 1: passing the `GITHUB_TOKEN` as an input
 
-This example workflow uses the [labeler action](https://github.com/actions/labeler), which requires the `GITHUB_TOKEN` as the value for the `repo-token` input parameter:
-
-```yaml
-name: Pull request labeler
-
-on: [ pull_request_target ]
-
-{% ifversion fpt or ghes > 3.1 or ghae or ghec %}permissions:
-  contents: read
-  pull-requests: write
-
-{% endif %}
-jobs:
-  triage:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/labeler@v2
-        with:
-          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
-```
+{% data reusables.github-actions.github_token-input-example %}
 
 ### Example 2: calling the REST API
 
diff --git a/content/actions/security-guides/encrypted-secrets.md b/content/actions/security-guides/encrypted-secrets.md
index ba0efc7bc1..3aab5563cf 100644
--- a/content/actions/security-guides/encrypted-secrets.md
+++ b/content/actions/security-guides/encrypted-secrets.md
@@ -53,11 +53,7 @@ To make a secret available to an action, you must set the secret as an input or
 
 You can use and read encrypted secrets in a workflow file if you have access to edit the file. For more information, see "[Access permissions on {% data variables.product.prodname_dotcom %}](/github/getting-started-with-github/access-permissions-on-github)."
 
-{% warning %}
-
-**Warning:** {% data variables.product.prodname_dotcom %} automatically redacts secrets printed to the log, but you should avoid printing secrets to the log intentionally.
-
-{% endwarning %}
+{% data reusables.github-actions.secrets-redaction-warning %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 Organization and repository secrets are read when a workflow run is queued, and environment secrets are read when a job referencing the environment starts.
diff --git a/data/reusables/actions/context-contents.md b/data/reusables/actions/context-contents.md
new file mode 100644
index 0000000000..30bc347f8c
--- /dev/null
+++ b/data/reusables/actions/context-contents.md
@@ -0,0 +1 @@
+Contexts, objects, and properties will vary significantly under different workflow run conditions.
\ No newline at end of file
diff --git a/data/reusables/actions/context-example-note.md b/data/reusables/actions/context-example-note.md
new file mode 100644
index 0000000000..a93d9bd5d7
--- /dev/null
+++ b/data/reusables/actions/context-example-note.md
@@ -0,0 +1,5 @@
+{% note %}
+
+**Note:** This context is an example only. The contents of a context depends on the workflow that you are running. {% data reusables.actions.context-contents %}
+
+{% endnote %}
diff --git a/data/reusables/actions/runner-arch-description.md b/data/reusables/actions/runner-arch-description.md
index d3b8df34bc..60a9d02739 100644
--- a/data/reusables/actions/runner-arch-description.md
+++ b/data/reusables/actions/runner-arch-description.md
@@ -1 +1 @@
-The architecture of the runner executing the job. Possible values are `X86`, `X64`, `ARM`, and `ARM64`.
+The architecture of the runner executing the job. Possible values are `X86`, `X64`, `ARM`, or `ARM64`.
diff --git a/data/reusables/actions/runner-tool-cache-description.md b/data/reusables/actions/runner-tool-cache-description.md
index d9674e8737..3b260a9896 100644
--- a/data/reusables/actions/runner-tool-cache-description.md
+++ b/data/reusables/actions/runner-tool-cache-description.md
@@ -1 +1 @@
-The path to the directory containing preinstalled tools for {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[Specifications for {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
+The path to the directory containing preinstalled tools for {% data variables.product.prodname_dotcom %}-hosted runners. For more information, see "[About {% data variables.product.prodname_dotcom %}-hosted runners](/actions/reference/specifications-for-github-hosted-runners/#supported-software)".
diff --git a/data/reusables/github-actions/github_token-input-example.md b/data/reusables/github-actions/github_token-input-example.md
new file mode 100644
index 0000000000..be3cdbbbd7
--- /dev/null
+++ b/data/reusables/github-actions/github_token-input-example.md
@@ -0,0 +1,19 @@
+This example workflow uses the [labeler action](https://github.com/actions/labeler), which requires the `GITHUB_TOKEN` as the value for the `repo-token` input parameter:
+
+```yaml{:copy}
+name: Pull request labeler
+on: [ pull_request_target ]
+
+{% ifversion fpt or ghes > 3.1 or ghae or ghec %}permissions:
+  contents: read
+  pull-requests: write
+
+{% endif %}
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/labeler@v2
+        with:
+          repo-token: {% raw %}${{ secrets.GITHUB_TOKEN }}{% endraw %}
+```
diff --git a/data/reusables/github-actions/run_id_description.md b/data/reusables/github-actions/run_id_description.md
index e47047c28c..bf50c00c48 100644
--- a/data/reusables/github-actions/run_id_description.md
+++ b/data/reusables/github-actions/run_id_description.md
@@ -1 +1 @@
-A unique number for each run within a repository. This number does not change if you re-run the workflow run.
+A unique number for each workflow run within a repository. This number does not change if you re-run the workflow run.
diff --git a/data/reusables/github-actions/secrets-redaction-warning.md b/data/reusables/github-actions/secrets-redaction-warning.md
new file mode 100644
index 0000000000..8f1eda7119
--- /dev/null
+++ b/data/reusables/github-actions/secrets-redaction-warning.md
@@ -0,0 +1,5 @@
+{% warning %}
+
+**Warning:** {% data variables.product.prodname_dotcom %} automatically redacts secrets printed to the log, but you should avoid printing secrets to the log intentionally.
+
+{% endwarning %}
\ No newline at end of file