diff --git a/assets/images/help/saml/okta-add-application.png b/assets/images/help/saml/okta-add-application.png
deleted file mode 100644
index cb7438e952..0000000000
Binary files a/assets/images/help/saml/okta-add-application.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-add-ghec-application.png b/assets/images/help/saml/okta-add-ghec-application.png
deleted file mode 100644
index a5632b64bf..0000000000
Binary files a/assets/images/help/saml/okta-add-ghec-application.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-admin-button.png b/assets/images/help/saml/okta-admin-button.png
deleted file mode 100644
index 0746f748bf..0000000000
Binary files a/assets/images/help/saml/okta-admin-button.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-application-label.png b/assets/images/help/saml/okta-application-label.png
deleted file mode 100644
index d596c23dcb..0000000000
Binary files a/assets/images/help/saml/okta-application-label.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-applications.png b/assets/images/help/saml/okta-applications.png
deleted file mode 100644
index 3abdbe83df..0000000000
Binary files a/assets/images/help/saml/okta-applications.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-authenticate-with-ghec-organization.png b/assets/images/help/saml/okta-authenticate-with-ghec-organization.png
deleted file mode 100644
index 557ff4860e..0000000000
Binary files a/assets/images/help/saml/okta-authenticate-with-ghec-organization.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-configure-api-integration.png b/assets/images/help/saml/okta-configure-api-integration.png
deleted file mode 100644
index 27b80d7125..0000000000
Binary files a/assets/images/help/saml/okta-configure-api-integration.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-enable-api-integration.png b/assets/images/help/saml/okta-enable-api-integration.png
deleted file mode 100644
index ab4a9ea7cf..0000000000
Binary files a/assets/images/help/saml/okta-enable-api-integration.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-github-enterprises.png b/assets/images/help/saml/okta-github-enterprises.png
deleted file mode 100644
index 2f0edf4e5d..0000000000
Binary files a/assets/images/help/saml/okta-github-enterprises.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-github-organization-name.png b/assets/images/help/saml/okta-github-organization-name.png
deleted file mode 100644
index e7d5839f31..0000000000
Binary files a/assets/images/help/saml/okta-github-organization-name.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-enable-create-users.png b/assets/images/help/saml/okta-provisioning-enable-create-users.png
deleted file mode 100644
index 5c8fd0cf21..0000000000
Binary files a/assets/images/help/saml/okta-provisioning-enable-create-users.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png b/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png
deleted file mode 100644
index 83dcc5c3be..0000000000
Binary files a/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-enable-options.png b/assets/images/help/saml/okta-provisioning-enable-options.png
new file mode 100644
index 0000000000..114532a138
Binary files /dev/null and b/assets/images/help/saml/okta-provisioning-enable-options.png differ
diff --git a/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png b/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png
deleted file mode 100644
index a1ef0384b9..0000000000
Binary files a/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-save.png b/assets/images/help/saml/okta-provisioning-save.png
deleted file mode 100644
index 8c65117baf..0000000000
Binary files a/assets/images/help/saml/okta-provisioning-save.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-tab-save.png b/assets/images/help/saml/okta-provisioning-tab-save.png
deleted file mode 100644
index 8c36e4b621..0000000000
Binary files a/assets/images/help/saml/okta-provisioning-tab-save.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-provisioning-tab.png b/assets/images/help/saml/okta-provisioning-tab.png
index d5d76dcdd5..206b128a0e 100644
Binary files a/assets/images/help/saml/okta-provisioning-tab.png and b/assets/images/help/saml/okta-provisioning-tab.png differ
diff --git a/assets/images/help/saml/okta-provisioning-to-app-edit-button.png b/assets/images/help/saml/okta-provisioning-to-app-edit-button.png
index bfd957fe4f..9ec796059d 100644
Binary files a/assets/images/help/saml/okta-provisioning-to-app-edit-button.png and b/assets/images/help/saml/okta-provisioning-to-app-edit-button.png differ
diff --git a/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png b/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png
deleted file mode 100644
index ebb2dd9834..0000000000
Binary files a/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-search-for-an-application.png b/assets/images/help/saml/okta-search-for-an-application.png
deleted file mode 100644
index c0c9205bef..0000000000
Binary files a/assets/images/help/saml/okta-search-for-an-application.png and /dev/null differ
diff --git a/assets/images/help/saml/okta-sign-on-tab.png b/assets/images/help/saml/okta-sign-on-tab.png
index 35f6351647..e907d72d14 100644
Binary files a/assets/images/help/saml/okta-sign-on-tab.png and b/assets/images/help/saml/okta-sign-on-tab.png differ
diff --git a/assets/images/help/saml/okta-view-setup-instructions.png b/assets/images/help/saml/okta-view-setup-instructions.png
deleted file mode 100644
index 52617c042f..0000000000
Binary files a/assets/images/help/saml/okta-view-setup-instructions.png and /dev/null differ
diff --git a/content/actions/learn-github-actions/environment-variables.md b/content/actions/learn-github-actions/environment-variables.md
index 83e39ee23f..315f0e46a1 100644
--- a/content/actions/learn-github-actions/environment-variables.md
+++ b/content/actions/learn-github-actions/environment-variables.md
@@ -18,83 +18,188 @@ versions:
 
 ## About environment variables
 
-{% data variables.product.prodname_dotcom %} sets default environment variables that are available to every step in a workflow run. Environment variables are case-sensitive. Commands run in actions or steps can create, read, and modify environment variables.
+You can use environment variables to store information that you want to reference in your workflow. You reference environment variables within a workflow step or an action, and the variables are interpolated on the runner machine that runs your workflow. Commands that run in actions or workflow steps can create, read, and modify environment variables.
 
-To set custom environment variables, you need to specify the variables in the workflow file. You can define environment variables for a step, job, or entire workflow using the [`jobs.<job_id>.steps[*].env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsenv), [`jobs.<job_id>.env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#jobsjob_idenv), and [`env`](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions#env) keywords. For more information, see "[Workflow syntax for {% data variables.product.prodname_dotcom %}](/articles/workflow-syntax-for-github-actions/#jobsjob_idstepsenv)."
+You can set your own custom environment variables, you can use the default environment variables that {% data variables.product.prodname_dotcom %} sets automatically, and you can also use any other environment variables that are set in the working environment on the runner. Environment variables are case-sensitive. 
+
+To set a custom environment variable, you must define it in the workflow file. The scope of a custom environment variable is limited to the element in which it is defined. You can define environment variables that are scoped for:
+
+* The entire workflow, by using [`env`](/actions/using-workflows/workflow-syntax-for-github-actions#env) at the top level of the workflow file.
+* The contents of a job within a workflow, by using [`jobs.<job_id>.env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idenv).
+* A specific step within a job, by using [`jobs.<job_id>.steps[*].env`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsenv).
 
 {% raw %}
 ```yaml
+name: Greeting on variable day
+
+on:
+  workflow_dispatch
+
+env:
+  DAY_OF_WEEK: Monday
+
 jobs:
-  weekday_job:
+  greeting_job:
     runs-on: ubuntu-latest
     env:
-      DAY_OF_WEEK: Mon
+      Greeting: Hello
     steps:
-      - name: "Hello world when it's Monday"
-        if: ${{ env.DAY_OF_WEEK == 'Mon' }}
-        run: echo "Hello $FIRST_NAME $middle_name $Last_Name, today is Monday!"
+      - name: "Say Hello Mona it's Monday"
+        run: echo "$Greeting $First_Name. Today is $DAY_OF_WEEK!"
         env:
-          FIRST_NAME: Mona
-          middle_name: The
-          Last_Name: Octocat
+          First_Name: Mona
 ```
 {% endraw %}
 
-To use the value of an environment variable in a workflow file, you should use the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context). If you want to use the value of an environment variable inside a runner, you can use the runner operating system's normal method for reading environment variables.
+The example above shows three custom environment variables being used in an `echo` command: `$DAY_OF_WEEK`, `$Greeting`, and  `$First_Name`. The values for these environment variables are set, and scoped, at the workflow, job, and step level respectively. 
 
-If you use the workflow file's `run` key to read environment variables from within the runner operating system (as shown in the example above), the variable is substituted in the runner operating system after the job is sent to the runner. For other parts of a workflow file, you must use the `env` context to read environment variables; this is because workflow keys (such as `if`) require the variable to be substituted during workflow processing before it is sent to the runner.
+Because environment variable interpolation is done after a workflow job is sent to a runner machine, you must use the appropriate syntax for the shell that's used on the runner. In this example, the workflow specifies `ubuntu-latest`. By default, Linux runners use the bash shell, so you must use the syntax `$NAME`. If the workflow specified a Windows runner, you would use the syntax for PowerShell, `$env:NAME`. For more information about shells, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsshell)."
 
-You can also use the `GITHUB_ENV` environment file to set an environment variable that the following steps in a job can use. The environment file can be used directly by an action or as a shell command in a workflow file using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)."
+{% note %}
+
+**Note**: You can list the entire set of environment variables that are available to a workflow step by using <span style="white-space: nowrap;">`run: env`</span> in a step and then examining the output for the step.
+
+{% endnote %}
+
+## Using contexts to access environment variable values
+
+In addition to environment variables, {% data variables.product.prodname_actions %} also allows you to set and read values using contexts. Environment variables and contexts are intended for use at different points in the workflow.
+
+Environment variables are always interpolated on the virtual machine runner. However, parts of a workflow are processed by {% data variables.product.prodname_actions %} and are not sent to the runner. You cannot use environment variables in these parts of a workflow file. Instead, you can use contexts. For example, an `if` conditional, which determines whether a job or step is sent to the runner, is always processed by {% data variables.product.prodname_actions %}. You can use a context in an `if` conditional statement to access the value of an environment variable.
+
+{% raw %}
+```yaml
+env:
+  DAY_OF_WEEK: Monday
+
+jobs:
+  greeting_job:
+    runs-on: ubuntu-latest
+    env:
+      Greeting: Hello
+    steps:
+      - name: "Say Hello Mona it's Monday"
+        if: ${{ env.DAY_OF_WEEK == 'Monday' }}
+        run: echo "$Greeting $First_Name. Today is $DAY_OF_WEEK!"
+        env:
+          First_Name: Mona
+```
+{% endraw %}
+
+In this modification of the first example, we've introduced an `if` conditional. The workflow step is now only run if `DAYS_OF_WEEK` is set to "Monday". We access this value from the `if` conditional statement by using the [`env` context](/actions/learn-github-actions/contexts#env-context).
+
+{% note %}
+
+**Note**: Contexts are usually denoted using the dollar sign and curly braces, as {% raw %}`${{ context.property }}`{% endraw %}. In an `if` conditional, the {% raw %}`${{` and `}}`{% endraw %} are optional, but if you use them they must enclose the entire comparison statement, as shown above. 
+
+{% endnote %}
+
+You will commonly use either the `env` or `github` context to access environment variable values in parts of the workflow that are processed before jobs are sent to runners. 
+
+
+| Context | Use case | Example |
+| --- | --- | --- |
+| `env` | Reference custom environment variables defined in the workflow. | <span style="white-space: nowrap;">{% raw %}`${{ env.MY_VARIABLE }}`{% endraw %}</span> |
+| `github` | Reference information about the workflow run and the event that triggered the run. | <span style="white-space: nowrap;">{% raw %}`${{ github.repository }}`{% endraw %}</span> |
+
+
+ 
+There are many other contexts that you can use for a variety of purposes in your workflows. For more information, see "[Contexts](/actions/learn-github-actions/contexts)." For details of where you can use specific contexts within a workflow, see "[Context availability](/actions/learn-github-actions/contexts#context-availability)."
+
+### Other types of variables
+
+In most places in a workflow, the only types of variables that you can use are either environment variables, such as `$MY_VARIABLE`, or the equivalent context property, such as <span style="white-space: nowrap;">{% raw %}`${{ env.MY_VARIABLE }}`{% endraw %}</span>. Exceptions are:
+
+* Inputs for the `workflow_call` and `workflow_dispatch` events, which allow you to pass values to a workflow. For more information, see [`on.workflow_call.inputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_callinputs) and [`on.workflow_dispatch.inputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#onworkflow_dispatchinputs).
+* Job outputs, which allow you to pass values between jobs in a workflow. For more information, see [`jobs.<job_id>.outputs`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs).
+* The variables in a format expression, which allow you to replace parts of a string. For more information, see [`format`](/actions/learn-github-actions/expressions#format).
+
+## Naming conventions for environment variables
+
+When you set a custom environment variable, you cannot use any of the default environment variable names. For a complete list of these, see "[Default environment variables](#default-environment-variables)" below. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
+
+Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `HOME`, `GITHUB_ENV`, and `GITHUB_WORKSPACE` default environment variables are exceptions to this convention.
 
 ## Default environment variables
 
+The default environment variables that {% data variables.product.prodname_dotcom %} sets are available to every step in a workflow. 
+
 We strongly recommend that actions use environment variables to access the filesystem rather than using hardcoded file paths. {% data variables.product.prodname_dotcom %} sets environment variables for actions to use in all runner environments.
 
 | Environment variable | Description |
 | ---------------------|------------ |
 | `CI` | Always set to `true`. |
-| `GITHUB_WORKFLOW` | The name of the workflow. |
-| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} |
-| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} |
-| `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. |
-| `GITHUB_ACTION` | The unique identifier (`id`) of the action. |
-| `GITHUB_ACTION_PATH` | The path where your action is located. You can use this path to access files located in the same repository as your action. This variable is only supported in composite actions. |
+| `GITHUB_ACTION` | The name of the action currently running, or the [`id`](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idstepsid) of a step. For example, for an action, `__repo-owner_name-of-action-repo`.<br><br>{% 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 script or action more than once in the same job, the name will include a suffix that consists of the sequence number preceded by an underscore. 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` | 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. For example, `/home/runner/work/_actions/repo-owner/name-of-action-repo/v1`. |
+| `GITHUB_ACTION_REPOSITORY` | For a step executing an action, this is the owner and repository name of the action. For example, `actions/checkout`. |
 | `GITHUB_ACTIONS` | Always set to `true` when {% data variables.product.prodname_actions %} is running the workflow. You can use this variable to differentiate when tests are being run locally or by {% data variables.product.prodname_actions %}.
 | `GITHUB_ACTOR` | The name of the person or app that initiated the workflow. For example, `octocat`. |
-| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
-| `GITHUB_EVENT_NAME` | The name of the webhook event that triggered the workflow. |
-| `GITHUB_EVENT_PATH` | The path of the file with the complete webhook event payload. For example, `/github/workflow/event.json`. |
-| `GITHUB_WORKSPACE` | The {% data variables.product.prodname_dotcom %} workspace directory path, initially empty. For example, `/home/runner/work/my-repo-name/my-repo-name`. The [actions/checkout](https://github.com/actions/checkout) action will check out files, by default a copy of your repository, within this directory. |
-| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
-| `GITHUB_REF` | The branch or tag ref that triggered the workflow. For example, `refs/heads/feature-branch-1`. If neither a branch or tag is available for the event type, the variable will not exist. |
+| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
+| `GITHUB_BASE_REF` | The name of the base ref or target branch of the pull request in a workflow run. This is only set when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. For example, `main`. |
+| `GITHUB_ENV` | The path on the runner to the file that sets environment variables from workflow commands. This file is unique to the current step and changes for each step in a job. For example, `/home/runner/work/_temp/_runner_file_commands/set_env_87406d6e-4979-4d42-98e1-3dab1f48b13a`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable)." | 
+| `GITHUB_EVENT_NAME` | The name of the event that triggered the workflow. For example, `workflow_dispatch`. |
+| `GITHUB_EVENT_PATH` | The path to the file on the runner that contains the full event webhook payload. For example, `/github/workflow/event.json`. |
+| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
+| `GITHUB_HEAD_REF` | The head ref or source branch of the pull request in a workflow run. This property is only set when the event that triggers a workflow run is either `pull_request` or `pull_request_target`. For example, `feature-branch-1`. |
+| `GITHUB_JOB` | The [job_id](/actions/reference/workflow-syntax-for-github-actions#jobsjob_id) of the current job. For example, `greeting_job`. |
+| `GITHUB_PATH` | The path on the runner to the file that sets system `PATH` variables from workflow commands. This file is unique to the current step and changes for each step in a job.  For example, `/home/runner/work/_temp/_runner_file_commands/add_path_899b9445-ad4a-400c-aa89-249f18632cf5`. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-commands-for-github-actions#adding-a-system-path)." |
+| `GITHUB_REF` | 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>`. This variable is only set if a branch or tag is available for the event type. For example, `refs/heads/feature-branch-1`. |
 {%- ifversion fpt or ghec or ghes > 3.3 or ghae-issue-5338 %}
-| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} |
+| `GITHUB_REF_NAME` | {% data reusables.actions.ref_name-description %} For example, `feature-branch-1`.|
 | `GITHUB_REF_PROTECTED` | {% data reusables.actions.ref_protected-description %} |
 | `GITHUB_REF_TYPE` | {% data reusables.actions.ref_type-description %} |
 {%- endif %}
-| `GITHUB_HEAD_REF` | Only set for pull request events. The name of the head branch.
-| `GITHUB_BASE_REF` | Only set for pull request events. The name of the base branch.
-| `GITHUB_SERVER_URL`| Returns the URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.
-| `GITHUB_API_URL` | Returns the API URL. For example: `{% data variables.product.api_url_code %}`.
-| `GITHUB_GRAPHQL_URL` | Returns the GraphQL API URL. For example: `{% data variables.product.graphql_url_code %}`.
-| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %}
-| `RUNNER_OS` | {% data reusables.actions.runner-os-description %}{% if actions-runner-arch-envvars %}
-| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}{% endif %}
-| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %}
-{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %}{% endif %}
+| `GITHUB_REPOSITORY` | The owner and repository name. For example, `octocat/Hello-World`. |
+| `GITHUB_REPOSITORY_OWNER` | The repository owner's name. For example, `octocat`. |
+| `GITHUB_RETENTION_DAYS` | The number of days that workflow run logs and artifacts are kept. For example, `90`. |
+| `GITHUB_RUN_ATTEMPT` | 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. For example, `3`. |
+| `GITHUB_RUN_ID` | {% data reusables.github-actions.run_id_description %} For example, `1658821493`. |
+| `GITHUB_RUN_NUMBER` | {% data reusables.github-actions.run_number_description %} For example, `3`. |
+| `GITHUB_SERVER_URL`| The URL of the {% data variables.product.product_name %} server. For example: `https://{% data variables.product.product_url %}`.
+| `GITHUB_SHA` | The commit SHA that triggered the workflow. For example, `ffac537e6cbbf934b08745a378932722df287a53`. |
+| `GITHUB_WORKFLOW` | The name of the workflow. For example, `My test workflow`. If the workflow file doesn't specify a `name`, the value of this variable is the full path of the workflow file in the repository. |
+| `GITHUB_WORKSPACE` | 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. For example, `/home/runner/work/my-repo-name/my-repo-name`. |
+{%- if actions-runner-arch-envvars %}
+| `RUNNER_ARCH` | {% data reusables.actions.runner-arch-description %}
+{%- endif %} |
+| `RUNNER_NAME` | {% data reusables.actions.runner-name-description %} For example, `Hosted Agent` |
+| `RUNNER_OS` | {% data reusables.actions.runner-os-description %} For example, `Windows` |
+| `RUNNER_TEMP` | {% data reusables.actions.runner-temp-directory-description %} For example, `D:\a\_temp` |
+{% ifversion not ghae %}| `RUNNER_TOOL_CACHE` | {% data reusables.actions.runner-tool-cache-description %} For example, `C:\hostedtoolcache\windows` |{% endif %}
 
-{% tip %}
+{% note %}
 
-**Note:** If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+**Note:** 
 
-{% endtip %}
+* If you need to use a workflow run's URL from within a job, you can combine these environment variables: `$GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID`
+* Most of the default environment variables have a corresponding, and similarly named, context property. For example, the value of the `GITHUB_REF` environment variable can be read during workflow processing using the {% raw %}`${{ github.ref }}`{% endraw %} context property.
 
-### Determining when to use default environment variables or contexts
+{% endnote %}
 
-{% data reusables.github-actions.using-context-or-environment-variables %}
+## Detecting the operating system
 
-## Naming conventions for environment variables
+You can write a single workflow file that can be used for different operating systems by using the `RUNNER_OS` default environment variable and the corresponding context property <span style="white-space: nowrap;">{% raw %}`${{ runner.os }}`{% endraw %}</span>. For example, the following workflow could be run successfully if you changed the operating system from `macos-latest` to `windows-latest` without having to alter the syntax of the environment variables, which differs depending on the shell being used by the runner.
 
-When you set a custom environment variable, you cannot use any of the default environment variable names listed above with the prefix `GITHUB_`. If you attempt to override the value of one of these default environment variables, the assignment is ignored.
+{% raw %}
+```yaml
+jobs:
+  if-Windows-else:
+    runs-on: macos-latest
+    steps:
+      - name: condition 1
+        if: runner.os == 'Windows'
+        run: echo "The operating system on the runner is $env:RUNNER_OS."
+      - name: condition 2
+        if: runner.os != 'Windows'
+        run: echo "The operating system on the runner is not Windows, it's $RUNNER_OS."
+```
+{% endraw %}
 
-Any new environment variables you set that point to a location on the filesystem should have a `_PATH` suffix. The `HOME` and `GITHUB_WORKSPACE` default variables are exceptions to this convention because the words "home" and "workspace" already imply a location.
+In this example, the two `if` statements check the `os` property of the `runner` context to determine the operating system of the runner. `if` conditionals are processed by {% data variables.product.prodname_actions %}, and only steps where the check resolves as `true` are sent to the runner. Here one of the checks will always be `true` and the other `false`, so only one of these steps is sent to the runner. Once the job is sent to the runner, the step is executed and the environment variable in the `echo` command is interpolated using the appropriate syntax (`$env:NAME` for PowerShell on Windows, and `$NAME` for bash and sh on Linux and MacOS). In this example, the statement `runs-on: macos-latest` means that the second step will be run.
+
+## Passing values between steps and jobs in a workflow
+
+ If you generate a value in one step of a job, you can use the value in subsequent steps of the same job by assigning the value to an existing or new environment variable and then writing this to the `GITHUB_ENV` environment file. The environment file can be used directly by an action, or from a shell command in the workflow file by using the `run` keyword. For more information, see "[Workflow commands for {% data variables.product.prodname_actions %}](/actions/reference/workflow-commands-for-github-actions/#setting-an-environment-variable)." 
+ 
+ If you want to pass a value from a step in one job in a workflow to a step in another job in the workflow, you can define the value as a job output. You can then reference this job output from a step in another job. For more information, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/learn-github-actions/workflow-syntax-for-github-actions#jobsjob_idoutputs)." 
+ 
\ No newline at end of file
diff --git a/content/actions/learn-github-actions/expressions.md b/content/actions/learn-github-actions/expressions.md
index 95646a2618..5d2648b35c 100644
--- a/content/actions/learn-github-actions/expressions.md
+++ b/content/actions/learn-github-actions/expressions.md
@@ -15,7 +15,7 @@ miniTocMaxHeadingLevel: 3
 
 ## About expressions
 
-You can use expressions to programmatically set variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
+You can use expressions to programmatically set environment variables in workflow files and access contexts. An expression can be any combination of literal values, references to a context, or functions. You can combine literals, context references, and functions using operators. For more information about contexts, see "[Contexts](/actions/learn-github-actions/contexts)."
 
 Expressions are commonly used with the conditional `if` keyword in a workflow file to determine whether a step should run. When an `if` conditional is `true`, the step will run.
 
@@ -55,7 +55,7 @@ As part of an expression, you can use `boolean`, `null`, `number`, or `string` d
 | `boolean` | `true` or `false` |
 | `null`    | `null` |
 | `number`  | Any number format supported by JSON. |
-| `string`  | You must use single quotes. Escape literal single-quotes with a single quote. |
+| `string`  | You don't need to enclose strings in {% raw %}${{{% endraw %} and {% raw %}}}{% endraw %}. However, if you do, you must use single quotes around the string and escape literal single quotes with an additional single quote. |
 
 #### Example
 
@@ -68,8 +68,8 @@ env:
   myFloatNumber: ${{ -9.2 }}
   myHexNumber: ${{ 0xff }}
   myExponentialNumber: ${{ -2.99-e2 }}
-  myString: ${{ 'Mona the Octocat' }}
-  myEscapedString: ${{ 'It''s open source!' }}
+  myString: Mona the Octocat
+  myStringInBraces: ${{ 'It''s open source!' }}
 ```
 {% endraw %}
 
@@ -252,7 +252,7 @@ jobs:
 
 Returns a single hash for the set of files that matches the `path` pattern. You can provide a single `path` pattern or multiple `path` patterns separated by commas. The `path` is relative to the `GITHUB_WORKSPACE` directory and can only include files inside of the `GITHUB_WORKSPACE`. This function calculates an individual SHA-256 hash for each matched file, and then uses those hashes to calculate a final SHA-256 hash for the set of files. For more information about SHA-256, see "[SHA-2](https://en.wikipedia.org/wiki/SHA-2)."
 
-You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/github/automating-your-workflow-with-github-actions/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
+You can use pattern matching characters to match file names. Pattern matching is case-insensitive on Windows. For more information about supported pattern matching characters, see "[Workflow syntax for {% data variables.product.prodname_actions %}](/actions/using-workflows/workflow-syntax-for-github-actions/#filter-pattern-cheat-sheet)."
 
 #### Example with a single pattern
 
diff --git a/content/actions/using-jobs/assigning-permissions-to-jobs.md b/content/actions/using-jobs/assigning-permissions-to-jobs.md
index 0fdc896e72..a99c44cd87 100644
--- a/content/actions/using-jobs/assigning-permissions-to-jobs.md
+++ b/content/actions/using-jobs/assigning-permissions-to-jobs.md
@@ -5,7 +5,7 @@ intro: Modify the default permissions granted to `GITHUB_TOKEN`.
 versions:
   fpt: '*'
   ghes: '> 3.1'
-  ghae: 'ghae-next'
+  ghae: '*'
   ghec: '*'
 miniTocMaxHeadingLevel: 4
 ---
diff --git a/content/actions/using-jobs/using-concurrency.md b/content/actions/using-jobs/using-concurrency.md
index 872111096c..0adbbe915a 100644
--- a/content/actions/using-jobs/using-concurrency.md
+++ b/content/actions/using-jobs/using-concurrency.md
@@ -5,7 +5,7 @@ intro: Run a single job at a time.
 versions:
   fpt: '*'
   ghes: '> 3.1'
-  ghae: 'ghae-next'
+  ghae: '*'
   ghec: '*'
 miniTocMaxHeadingLevel: 4
 ---
diff --git a/content/actions/using-workflows/workflow-commands-for-github-actions.md b/content/actions/using-workflows/workflow-commands-for-github-actions.md
index 6486e941a2..efafd3e485 100644
--- a/content/actions/using-workflows/workflow-commands-for-github-actions.md
+++ b/content/actions/using-workflows/workflow-commands-for-github-actions.md
@@ -307,7 +307,7 @@ The `STATE_processID` variable is then exclusively available to the cleanup scri
 console.log("The running PID from the main action is: " +  process.env.STATE_processID);
 ```
 
-## Environment Files
+## Environment files
 
 During the execution of a workflow, the runner generates temporary files that can be used to perform certain actions. The path to these files are exposed via environment variables. You will need to use UTF-8 encoding when writing to these files to ensure proper processing of the commands. Multiple commands can be written to the same file, separated by newlines.
 
@@ -345,16 +345,10 @@ More detail about UTF-8 and PowerShell Core found on this great [Stack Overflow
 ## Setting an environment variable
 
 ``` bash
-echo "{name}={value}" >> $GITHUB_ENV
+echo "{environment_variable_name}={value}" >> $GITHUB_ENV
 ```
 
-Creates or updates an environment variable for any steps running next in a job. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. Environment variables are case-sensitive and you can include punctuation.
-
-{% note %}
-
-**Note:** Environment variables must be explicitly referenced using the [`env` context](/actions/reference/context-and-expression-syntax-for-github-actions#env-context) in expression syntax or through use of the `$GITHUB_ENV` file directly; environment variables are not implicitly available in shell commands.
-
-{% endnote %}
+You can make an environment variable available to any subsequent steps in a workflow job by defining or updating the environment variable and writing this to the `GITHUB_ENV` environment file. The step that creates or updates the environment variable does not have access to the new value, but all subsequent steps in a job will have access. The names of environment variables are case-sensitive, and you can include punctuation. For more information, see "[Environment variables](/actions/learn-github-actions/environment-variables)."
 
 ### Example
 
diff --git a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
index 3daac40f58..8a2e9cc3af 100644
--- a/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
+++ b/content/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta.md
@@ -15,7 +15,6 @@ topics:
 type: how_to
 shortTitle: Configure SAML with Okta
 ---
-{% data reusables.enterprise-accounts.user-provisioning-release-stage %}
 
 {% data reusables.enterprise-accounts.emu-saml-note %}
 
@@ -27,27 +26,20 @@ SAML SSO controls and secures access to enterprise account resources like organi
 
 {% data reusables.saml.switching-from-org-to-enterprise %} For more information, see "[Switching your SAML configuration from an organization to an enterprise account](/github/setting-up-and-managing-your-enterprise/configuring-identity-and-access-management-for-your-enterprise-account/switching-your-saml-configuration-from-an-organization-to-an-enterprise-account)."
 
-## Prerequisites
-
-{% data reusables.saml.use-classic-ui %}
+Alternatively, you can also configure SAML SSO using Okta for an organization that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Configuring SAML single sign-on and SCIM using Okta](/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta)."
 
 ## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
 
-{% data reusables.saml.okta-admin-button %}
+{% data reusables.saml.okta-sign-into-your-account %}
+1. Navigate to the [Github Enterprise Cloud - Enterprise Accounts](https://www.okta.com/integrations/github-enterprise-cloud-enterprise-accounts) application in the Okta Integration Network and click **Add Integration**.
 {% data reusables.saml.okta-dashboard-click-applications %}
-{% data reusables.saml.add-okta-application %}
-{% data reusables.saml.search-ghec-okta %}
-1. Click "{% data variables.product.prodname_ghe_cloud %} - Enterprise Accounts".
-1. Click **Add**.
 1. Optionally, to the right of "Application label", type a descriptive name for the application.
-  ![Application label field](/assets/images/help/saml/okta-application-label.png)
 1. To the right of "{% data variables.product.prodname_dotcom %} Enterprises", type the name of your enterprise account. For example, if your enterprise account's URL is `https://github.com/enterprises/octo-corp`, type `octo-corp`.
-  ![GitHub Enterprises field](/assets/images/help/saml/okta-github-enterprises.png)
 1. Click **Done**.
 
 ## Enabling and testing SAML SSO
 
-{% data reusables.saml.okta-admin-button %}
+{% data reusables.saml.okta-sign-into-your-account %}
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.click-enterprise-account-application %}
 {% data reusables.saml.assign-yourself-to-okta %}
@@ -64,17 +56,3 @@ SAML SSO controls and secures access to enterprise account resources like organi
 1. In Okta, create a group to match each organization owned by your enterprise account. The name of each group must match the account name of the organization (not the organization's display name). For example, if the URL of the organization is `https://github.com/octo-org`, name the group `octo-org`.
 1. Assign the application you created for your enterprise account to each group. {% data variables.product.prodname_dotcom %} will receive all `groups` data for each user.
 1. Add users to groups based on the organizations you'd like users to belong to.
-
-## Enabling SAML user provisioning
-
-{% data reusables.enterprise-accounts.access-enterprise %}
-{% data reusables.enterprise-accounts.settings-tab %}
-{% data reusables.enterprise-accounts.security-tab %}
-1. Under "SAML User Provisioning", select **Enable SAML user provisioning**.
-  ![Checkbox to enable user provisioning with SAML](/assets/images/help/business-accounts/user-provisioning.png)
-1. Click **Save**.
-1. Optionally, enable SAML user deprovisioning.
-   - Select **Enable SAML user deprovisioning**, then click **Save**.
-     ![Checkbox to enable user deprovisioning with SAML](/assets/images/help/business-accounts/saml-deprovisioning.png)
-   - Read the warning, then click **Enable SAML deprovisioning**.
-       ![Enable SAML deprovisioning button](/assets/images/help/business-accounts/saml-deprovisioning-confirm.png)
diff --git a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index bf47853ca9..d88ccb0c8f 100644
--- a/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -139,13 +139,15 @@ Replace the `autobuild` step with the same build commands you would use in produ
 For more information, see "[Configuring the {% data variables.product.prodname_codeql %} workflow for compiled languages](/code-security/secure-coding/configuring-the-codeql-workflow-for-compiled-languages#adding-build-steps-for-a-compiled-language)." 
 
 ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
-You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow:
+You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
+
 ```yaml
-- uses: actions/upload-artifact@v2
+- name: Initialize CodeQL
+  uses: github/codeql-action/init@v1
   with:
-    name: {% raw %}codeql-database-${{ matrix.language }}{% endraw %}
-    path: {% raw %}${{ runner.temp }}/codeql_databases{% endraw %}
+    debug: true
 ```
+
 This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
 
 The artifact will contain an archived copy of the source files scanned by {% data variables.product.prodname_codeql %} called _src.zip_. If you compare the source code files in the repository and the files in _src.zip_, you can see which types of file are missing. Once you know what types of file are not being analyzed, it is easier to understand how you may need to change the workflow for {% data variables.product.prodname_codeql %} analysis.
diff --git a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
index 7ef55ec4a7..d687f7760c 100644
--- a/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
+++ b/content/code-security/secret-scanning/defining-custom-patterns-for-secret-scanning.md
@@ -46,7 +46,16 @@ However, there can be situations where you want to scan for other secret pattern
 
 ## Regular expression syntax for custom patterns
 
-Custom patterns for {% data variables.product.prodname_secret_scanning %} are specified as regular expressions. {% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported.  For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation.
+Custom patterns for {% data variables.product.prodname_secret_scanning %} are specified as one or more regular expressions.
+
+- **Secret format:** an expression that describes the format of the secret itself.
+- **Before secret:** an expression that describes the characters that come before the secret. By default, this is set to `\A|[^0-9A-Za-z]` which means that the secret must be at the start of a line or be preceded by a non-alphanumeric character.
+- **After secret:** an expression that describes the characters that come after the secret. By default, this is set to `\z|[^0-9A-Za-z]` which means that the secret must be followed by a new line or a non-alphanumeric character.
+- **Additional match requirements:** one or more optional expressions that the secret itself must or must not match.
+
+For simple tokens you will usually only need to specify a secret format. The other fields provide flexibility so that you can specify more complex secrets without creating complex regular expressions.  For an example of a custom pattern, see "[Example of a custom pattern specified using additional requirements](#example-of-a-custom-pattern-specified-using-additional-requirements)" below.
+
+{% data variables.product.prodname_secret_scanning_caps %} uses the [Hyperscan library](https://github.com/intel/hyperscan) and only supports Hyperscan regex constructs, which are a subset of PCRE syntax. Hyperscan option modifiers are not supported.  For more information on Hyperscan pattern constructs, see "[Pattern support](http://intel.github.io/hyperscan/dev-reference/compilation.html#pattern-support)" in the Hyperscan documentation.
 
 ## Defining a custom pattern for a repository
 
@@ -61,6 +70,35 @@ Before defining a custom pattern, you must ensure that {% data variables.product
 
 After your pattern is created, {% data reusables.secret-scanning.secret-scanning-process %} For more information on viewing {% data variables.product.prodname_secret_scanning %} alerts, see "[Managing alerts from {% data variables.product.prodname_secret_scanning %}](/code-security/secret-security/managing-alerts-from-secret-scanning)."
 
+### Example of a custom pattern specified using additional requirements
+
+A company has an internal token with five characteristics. They use the different fields to specify how to identify tokens as follows:
+
+| **Characteristic** | **Field and regular expression** |
+|----------------|------------------------------|
+| Length between 5 and 10 characters | Secret format: `[$#%@AA-Za-z0-9]{5,10}` |
+| Does not end in a `.` | After secret: `[^\.]` |
+| Contains numbers and uppercase letters | Additional requirements: secret must match `[A-Z]` and `[0-9]` |
+| Does not include more than one lowercase letter in a row | Additional requirements: secret must not match `[a-z]{2,}` |
+| Contains one of `$%@!` | Additional requirements: secret must match `[$%@!]` |
+
+These tokens would match the custom pattern described above:
+
+```
+a9@AAfT!         # Secret string match: a9@AAfT
+ee95GG@ZA942@aa  # Secret string match: @ZA942@a
+a9@AA!ee9        # Secret string match: a9@AA
+```
+
+These strings would not match the custom pattern described above:
+
+```
+a9@AA.!
+a@AAAAA
+aa9@AA!ee9
+aAAAe9
+```
+
 ## Defining a custom pattern for an organization
 
 Before defining a custom pattern, you must ensure that you enable {% data variables.product.prodname_secret_scanning %} for the {% ifversion fpt or ghec %}private{% endif %} repositories that you want to scan in your organization. To enable {% data variables.product.prodname_secret_scanning %} on all {% ifversion fpt or ghec %}private{% endif %} repositories in your organization, see "[Managing security and analysis settings for your organization](/organizations/keeping-your-organization-secure/managing-security-and-analysis-settings-for-your-organization)."
diff --git a/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md b/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
index 0c2dba8ac3..59f97e484a 100644
--- a/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
+++ b/content/organizations/managing-saml-single-sign-on-for-your-organization/configuring-saml-single-sign-on-and-scim-using-okta.md
@@ -27,31 +27,25 @@ After you enable SCIM, the following provisioning features are available for any
 | Push Profile Updates | When you update a user's profile in Okta, Okta will update the metadata for the user's membership in your organization on {% data variables.product.product_location %}. |
 | Reactivate Users | When you reactivate a user in Okta, Okta will send an email invitation for the user to rejoin your organization on {% data variables.product.product_location %}. |
 
-## Prerequisites
-
-{% data reusables.saml.use-classic-ui %}
+Alternatively, you can configure SAML SSO for an enterprise using Okta. SCIM for enterprise accounts is only available with Enterprise Managed Users. For more information, see "[Configuring SAML single sign-on for your enterprise using Okta](/admin/identity-and-access-management/managing-iam-for-your-enterprise/configuring-saml-single-sign-on-for-your-enterprise-using-okta)" and "[Configuring SCIM provisioning for Enterprise Managed Users with Okta](/admin/identity-and-access-management/managing-iam-with-enterprise-managed-users/configuring-scim-provisioning-for-enterprise-managed-users-with-okta)."
 
 ## Adding the {% data variables.product.prodname_ghe_cloud %} application in Okta
 
-{% data reusables.saml.okta-dashboard-click-applications %}
-{% data reusables.saml.add-okta-application %}
-{% data reusables.saml.search-ghec-okta %}
-4. To the right of "Github Enterprise Cloud - Organization", click **Add**.
-  ![Clicking "Add" for the {% data variables.product.prodname_ghe_cloud %} application](/assets/images/help/saml/okta-add-ghec-application.png)
-
-5. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
-  ![Type GitHub organization name](/assets/images/help/saml/okta-github-organization-name.png)
-
-6. Click **Done**.
+{% data reusables.saml.okta-sign-into-your-account %}
+1. Navigate to the [Github Enterprise Cloud - Organization](https://www.okta.com/integrations/github-enterprise-cloud-organization) application in the Okta Integration Network and click **Add Integration**.
+1. Optionally, to the right of "Application label", type a descriptive name for the application.
+1. In the **GitHub Organization** field, type the name of your organization on {% data variables.product.product_location %}. For example, if your organization's URL is https://github.com/octo-org, the organization name would be `octo-org`.
+1. Click **Done**.
 
 ## Enabling and testing SAML SSO
 
+{% data reusables.saml.okta-sign-into-your-account %}
 {% data reusables.saml.okta-dashboard-click-applications %}
 {% data reusables.saml.okta-applications-click-ghec-application-label %}
 {% data reusables.saml.assign-yourself-to-okta %}
 {% data reusables.saml.okta-sign-on-tab %}
 {% data reusables.saml.okta-view-setup-instructions %}
-6. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization)."
+1. Enable and test SAML SSO on {% data variables.product.prodname_dotcom %} using the sign on URL, issuer URL, and public certificates from the "How to Configure SAML 2.0" guide. For more information, see "[Enabling and testing SAML single sign-on for your organization](/organizations/managing-saml-single-sign-on-for-your-organization/enabling-and-testing-saml-single-sign-on-for-your-organization#enabling-and-testing-saml-single-sign-on-for-your-organization)."
 
 ## Configuring access provisioning with SCIM in Okta
 
@@ -60,12 +54,9 @@ After you enable SCIM, the following provisioning features are available for any
 {% data reusables.saml.okta-provisioning-tab %}
 {% data reusables.saml.okta-configure-api-integration %}
 {% data reusables.saml.okta-enable-api-integration %}
+1. Click **Authenticate with Github Enterprise Cloud - Organization**.
+1. To the right of your organization's name, click **Grant**.
 
-
-6. Click **Authenticate with Github Enterprise Cloud - Organization**.
-  !["Authenticate with Github Enterprise Cloud - Organization" button for Okta application](/assets/images/help/saml/okta-authenticate-with-ghec-organization.png)
-
-7. To the right of your organization's name, click **Grant**.
   !["Grant" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-grant-organization-access.png)
 
   {% note %}
@@ -74,7 +65,6 @@ After you enable SCIM, the following provisioning features are available for any
 
   {% endnote %}
 1. Click **Authorize OktaOAN**.
-  !["Authorize OktaOAN" button for authorizing Okta SCIM integration to access organization](/assets/images/help/saml/okta-scim-integration-authorize-oktaoan.png)
 {% data reusables.saml.okta-save-provisioning %}
 {% data reusables.saml.okta-edit-provisioning %}
 
diff --git a/content/repositories/index.md b/content/repositories/index.md
index 1777d02c6d..abc6d5ee8e 100644
--- a/content/repositories/index.md
+++ b/content/repositories/index.md
@@ -1,6 +1,27 @@
 ---
 title: Repositories
 intro: Learn to use and manage the repositories that allow you to store and collaborate on your project's code.
+introLinks:
+  quickstart: /get-started/quickstart/create-a-repo
+  overview: /repositories/creating-and-managing-repositories/about-repositories
+featuredLinks:
+  guides:
+      - /repositories/creating-and-managing-repositories/cloning-a-repository
+      - /repositories/creating-and-managing-repositories/restoring-a-deleted-repository
+      - /repositories/working-with-files/managing-files/adding-a-file-to-a-repository
+      - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
+  popular:
+      - /repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches
+      - /repositories/releasing-projects-on-github/about-releases
+      - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-readmes
+      - /repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+  guideCards:
+    - /repositories/creating-and-managing-repositories/deleting-a-repository
+    - /repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule
+    - /repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/setting-repository-visibility
+changelog:
+  label: 'repos'
+layout: product-landing
 redirect_from:
   - /github/creating-cloning-and-archiving-repositories
 versions:
@@ -19,4 +40,3 @@ children:
   - /viewing-activity-and-data-for-your-repository
   - /archiving-a-github-repository
 ---
-
diff --git a/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
index 098eb78caf..93b62fddbf 100644
--- a/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
+++ b/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -5,7 +5,7 @@ Use the `paths` filter when you want to include file path patterns or when you w
 
 If you define both `branches`/`branches-ignore` and `paths`, the workflow will only run when both filters are satisfied.
 
-The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet]/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
+The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
 #### Example: Including paths
 
diff --git a/data/reusables/enterprise-accounts/user-provisioning-release-stage.md b/data/reusables/enterprise-accounts/user-provisioning-release-stage.md
deleted file mode 100644
index e9533a00f7..0000000000
--- a/data/reusables/enterprise-accounts/user-provisioning-release-stage.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{% note %}
-
-**Note:** User provisioning for organizations in your enterprise accounts, currently supported only for Okta, is in private beta and subject to change. To request access to the beta, [contact our account management team](https://enterprise.github.com/contact).
-
-{% endnote %}
diff --git a/data/reusables/saml/add-okta-application.md b/data/reusables/saml/add-okta-application.md
deleted file mode 100644
index 510991e221..0000000000
--- a/data/reusables/saml/add-okta-application.md
+++ /dev/null
@@ -1,2 +0,0 @@
-2. Click **Add application**.
-  !["Add application" button in the Okta Dashboard's Applications tab](/assets/images/help/saml/okta-add-application.png)
diff --git a/data/reusables/saml/okta-admin-button.md b/data/reusables/saml/okta-admin-button.md
deleted file mode 100644
index 80e9cb71b5..0000000000
--- a/data/reusables/saml/okta-admin-button.md
+++ /dev/null
@@ -1,2 +0,0 @@
-1. In Okta, in the upper-right corner, click **Admin**.
-  ![Admin button in Okta](/assets/images/help/saml/okta-admin-button.png)
diff --git a/data/reusables/saml/okta-applications-click-ghec-application-label.md b/data/reusables/saml/okta-applications-click-ghec-application-label.md
index f0e17be424..7619625cff 100644
--- a/data/reusables/saml/okta-applications-click-ghec-application-label.md
+++ b/data/reusables/saml/okta-applications-click-ghec-application-label.md
@@ -1,2 +1 @@
 1. In the list of applications, click the label for the application you created for the organization that uses {% data variables.product.prodname_ghe_cloud %}.
-  ![{% data variables.product.prodname_ghe_cloud %} application in Okta](/assets/images/help/saml/okta-ghec-application.png)
diff --git a/data/reusables/saml/okta-configure-api-integration.md b/data/reusables/saml/okta-configure-api-integration.md
index e9a2457dbd..958f43db02 100644
--- a/data/reusables/saml/okta-configure-api-integration.md
+++ b/data/reusables/saml/okta-configure-api-integration.md
@@ -1,2 +1 @@
 1. Click **Configure API Integration**.
-  !["Configure API Integration" button for Okta application](/assets/images/help/saml/okta-configure-api-integration.png)
diff --git a/data/reusables/saml/okta-dashboard-click-applications.md b/data/reusables/saml/okta-dashboard-click-applications.md
index 72d3851147..b875277236 100644
--- a/data/reusables/saml/okta-dashboard-click-applications.md
+++ b/data/reusables/saml/okta-dashboard-click-applications.md
@@ -1,2 +1 @@
-1. In the Okta Dashboard, click **Applications**.
-  !["Applications" item in the Okta Dashboard navigation bar](/assets/images/help/saml/okta-applications.png)
+1. In the left sidebar, use the **Applications** dropdown and click **Applications**.
diff --git a/data/reusables/saml/okta-edit-provisioning.md b/data/reusables/saml/okta-edit-provisioning.md
index 623630a71c..6767459d2d 100644
--- a/data/reusables/saml/okta-edit-provisioning.md
+++ b/data/reusables/saml/okta-edit-provisioning.md
@@ -1,11 +1,8 @@
-9. To avoid syncing errors and confirm that your users have SAML enabled and SCIM linked identities, we recommend you audit your organization's users. For more information, see "[Auditing users for missing SCIM metadata](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management#auditing-users-for-missing-scim-metadata)."
-10. To the right of "Provisioning to App", click **Edit**.
-  !["Edit" button for Okta application's provisioning options](/assets/images/help/saml/okta-provisioning-to-app-edit-button.png)
-11. To the right of "Create Users", select **Enable**.
-  !["Enable" checkbox for Okta application's "Create Users" option](/assets/images/help/saml/okta-provisioning-enable-create-users.png)
-12. To the right of "Update User Attributes", select **Enable**.
-  !["Enable" checkbox for Okta application's "Update User Attributes" option](/assets/images/help/saml/okta-provisioning-enable-update-user-attributes.png)
-13. To the right of "Deactivate Users", select **Enable**.
-  !["Enable" checkbox for Okta application's "Deactivate Users" option](/assets/images/help/saml/okta-provisioning-enable-deactivate-users.png)
-14. Click **Save**.
-  !["Save" button for Okta application's provisioning configuration](/assets/images/help/saml/okta-provisioning-save.png)
+1. To avoid syncing errors and confirm that your users have SAML enabled and SCIM linked identities, we recommend you audit your organization's users. For more information, see "[Auditing users for missing SCIM metadata](/organizations/managing-saml-single-sign-on-for-your-organization/troubleshooting-identity-and-access-management#auditing-users-for-missing-scim-metadata)."
+1. To the right of "Provisioning to App", click **Edit**.
+
+    ![Screenshot of "Edit" button for Okta application's provisioning options](/assets/images/help/saml/okta-provisioning-to-app-edit-button.png)
+1. To the right of **Create Users**, **Update User Attributes**, and **Deactivate Users**, select **Enable**.
+
+    ![Screenshot of "Enable" checkboxes for "Create Users", "Update User Attributes", and "Deactivate Users" options](/assets/images/help/saml/okta-provisioning-enable-options.png)
+1. Click **Save**.
diff --git a/data/reusables/saml/okta-enable-api-integration.md b/data/reusables/saml/okta-enable-api-integration.md
index 6b1aae4774..f11080d9fa 100644
--- a/data/reusables/saml/okta-enable-api-integration.md
+++ b/data/reusables/saml/okta-enable-api-integration.md
@@ -1,2 +1 @@
 1. Select **Enable API integration**.
-  !["Enable API integration" checkbox for Okta application](/assets/images/help/saml/okta-enable-api-integration.png)
diff --git a/data/reusables/saml/okta-provisioning-tab.md b/data/reusables/saml/okta-provisioning-tab.md
index 9db6e0e411..434d4d7ac0 100644
--- a/data/reusables/saml/okta-provisioning-tab.md
+++ b/data/reusables/saml/okta-provisioning-tab.md
@@ -1,2 +1,2 @@
 1. Under the name of the application, click **Provisioning**.
-  !["Provisioning" tab for Okta application](/assets/images/help/saml/okta-provisioning-tab.png)
+  ![Screenshot of "Provisioning" tab for Okta application](/assets/images/help/saml/okta-provisioning-tab.png)
diff --git a/data/reusables/saml/okta-save-provisioning.md b/data/reusables/saml/okta-save-provisioning.md
index a799e43fde..8fc5a5e979 100644
--- a/data/reusables/saml/okta-save-provisioning.md
+++ b/data/reusables/saml/okta-save-provisioning.md
@@ -1,2 +1 @@
 1. Click **Save**.
-  !["Save" button for Okta application's provisioning configuration](/assets/images/help/saml/okta-provisioning-tab-save.png)
diff --git a/data/reusables/saml/okta-sign-into-your-account.md b/data/reusables/saml/okta-sign-into-your-account.md
new file mode 100644
index 0000000000..7ff8f1679f
--- /dev/null
+++ b/data/reusables/saml/okta-sign-into-your-account.md
@@ -0,0 +1 @@
+1. Sign into your [Okta account](https://login.okta.com/).
diff --git a/data/reusables/saml/okta-sign-on-tab.md b/data/reusables/saml/okta-sign-on-tab.md
index 099407d979..ca034d1859 100644
--- a/data/reusables/saml/okta-sign-on-tab.md
+++ b/data/reusables/saml/okta-sign-on-tab.md
@@ -1,2 +1,2 @@
 1. Under the name of the application, click **Sign on**.
-  !["Sign on" tab for Okta application](/assets/images/help/saml/okta-sign-on-tab.png)
+  ![Screenshot of "Sign on" tab for Okta application](/assets/images/help/saml/okta-sign-on-tab.png)
diff --git a/data/reusables/saml/okta-view-setup-instructions.md b/data/reusables/saml/okta-view-setup-instructions.md
index 97185417fe..1e281f8d9d 100644
--- a/data/reusables/saml/okta-view-setup-instructions.md
+++ b/data/reusables/saml/okta-view-setup-instructions.md
@@ -1,2 +1 @@
 1. Under "SIGN ON METHODS", click **View Setup Instructions**.
-  !["View Setup Instructions" button in Okta application's "Sign On" tab](/assets/images/help/saml/okta-view-setup-instructions.png)
diff --git a/data/reusables/saml/search-ghec-okta.md b/data/reusables/saml/search-ghec-okta.md
deleted file mode 100644
index f2974c62e0..0000000000
--- a/data/reusables/saml/search-ghec-okta.md
+++ /dev/null
@@ -1,2 +0,0 @@
-3. In the search field, type "GitHub Enterprise Cloud".
-  ![Okta's "Search for an application" field](/assets/images/help/saml/okta-search-for-an-application.png)
diff --git a/docker-compose.prod.tmpl.yaml b/docker-compose.prod.tmpl.yaml
index dc43db072d..3c36bd2435 100644
--- a/docker-compose.prod.tmpl.yaml
+++ b/docker-compose.prod.tmpl.yaml
@@ -19,30 +19,14 @@ services:
       HEROKU_PRODUCTION_APP: true
       PORT: 4000
       DD_AGENT_HOST: datadog-agent
-    labels:
-      com.datadoghq.ad.logs: '[{"source": "node", "service": "docs"}]'
     depends_on:
       - datadog-agent
     restart: always
 
   datadog-agent:
-    image: datadog/agent:7.32.3
+    image: datadog/dogstatsd:7.32.4
     ports:
       - '8125:8125'
     environment:
       DD_API_KEY: ${DD_API_KEY}
-      DD_LOGS_ENABLED: true
-      DD_PROCESS_AGENT_ENABLED: true
-      DD_RUNTIME_METRICS_ENABLED: true
-      DD_DOGSTATSD_NON_LOCAL_TRAFFIC: true
       DD_AGENT_HOST: datadog-agent
-      DD_HEALTH_PORT: 5555
-      DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL: true
-      DD_LOGS_CONFIG_DOCKER_CONTAINER_USE_FILE: true
-      DD_CONTAINER_EXCLUDE: 'name:datadog-agent'
-      DD_DOGSTATSD_TAGS: 'service:ghdocs env:production'
-    volumes:
-      - /home/LogFiles:/var/lib/docker/containers:ro
-      - ${WEBAPP_STORAGE_HOME}/opt/datadog-agent/run:/opt/datadog-agent/run:rw
-      - /proc/:/host/proc/:ro
-      - /sys/fs/cgroup/:/host/sys/fs/cgroup:ro
diff --git a/lib/rest/static/decorated/api.github.com.json b/lib/rest/static/decorated/api.github.com.json
index 435d6d1aeb..5d8224b48e 100644
--- a/lib/rest/static/decorated/api.github.com.json
+++ b/lib/rest/static/decorated/api.github.com.json
@@ -9932,7 +9932,6 @@
     "x-github": {
       "githubCloudOnly": false,
       "enabledForGitHubApps": false,
-      "previews": [],
       "category": "enterprise-admin",
       "subcategory": "billing"
     },
@@ -14544,7 +14543,6 @@
     "x-github": {
       "githubCloudOnly": true,
       "enabledForGitHubApps": true,
-      "previews": [],
       "category": "teams",
       "subcategory": "external-groups"
     },
@@ -27102,7 +27100,6 @@
     "x-github": {
       "githubCloudOnly": false,
       "enabledForGitHubApps": true,
-      "previews": [],
       "category": "billing",
       "subcategory": null
     },
@@ -65689,7 +65686,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -65835,7 +65832,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -67804,7 +67801,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -67854,7 +67851,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/decorated/ghes-3.0.json b/lib/rest/static/decorated/ghes-3.0.json
index 3ae67887e5..aae7b35852 100644
--- a/lib/rest/static/decorated/ghes-3.0.json
+++ b/lib/rest/static/decorated/ghes-3.0.json
@@ -56962,7 +56962,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -57108,7 +57108,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -59141,7 +59141,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -59191,7 +59191,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/decorated/ghes-3.1.json b/lib/rest/static/decorated/ghes-3.1.json
index bde77947a9..5188773ef2 100644
--- a/lib/rest/static/decorated/ghes-3.1.json
+++ b/lib/rest/static/decorated/ghes-3.1.json
@@ -57629,7 +57629,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -57775,7 +57775,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -59808,7 +59808,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -59858,7 +59858,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/decorated/ghes-3.2.json b/lib/rest/static/decorated/ghes-3.2.json
index 09a05c80f3..b7d32dc62c 100644
--- a/lib/rest/static/decorated/ghes-3.2.json
+++ b/lib/rest/static/decorated/ghes-3.2.json
@@ -59808,7 +59808,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -59954,7 +59954,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -61987,7 +61987,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -62037,7 +62037,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/decorated/ghes-3.3.json b/lib/rest/static/decorated/ghes-3.3.json
index 4cf52d1903..7e9e131868 100644
--- a/lib/rest/static/decorated/ghes-3.3.json
+++ b/lib/rest/static/decorated/ghes-3.3.json
@@ -60050,7 +60050,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -60196,7 +60196,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -62165,7 +62165,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -62215,7 +62215,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/decorated/github.ae.json b/lib/rest/static/decorated/github.ae.json
index 0f4b95e243..311d2035a0 100644
--- a/lib/rest/static/decorated/github.ae.json
+++ b/lib/rest/static/decorated/github.ae.json
@@ -12065,7 +12065,6 @@
     "x-github": {
       "githubCloudOnly": true,
       "enabledForGitHubApps": true,
-      "previews": [],
       "category": "teams",
       "subcategory": "external-groups"
     },
@@ -51855,7 +51854,7 @@
       }
     ],
     "summary": "Create an issue",
-    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -52001,7 +52000,7 @@
     "categoryLabel": "Issues",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>Any user with pull access to a repository can create an issue. If <a href=\"https://help.github.com/articles/disabling-issues/\">issues are disabled in the repository</a>, the API returns a <code>410 Gone</code> status.</p>\n<p>This endpoint triggers <a href=\"https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "responses": [
       {
         "httpStatusCode": "201",
@@ -53970,7 +53969,7 @@
       }
     ],
     "summary": "Create an issue comment",
-    "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+    "description": "This endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
     "tags": [
       "issues"
     ],
@@ -54020,7 +54019,7 @@
     "subcategoryLabel": "Comments",
     "contentType": "application/json",
     "notes": [],
-    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
+    "descriptionHTML": "<p>This endpoint triggers <a href=\"https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications\">notifications</a>. Creating content too quickly using this endpoint may result in secondary rate limiting. See \"<a href=\"https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\">Secondary rate limits</a>\" and \"<a href=\"https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits\">Dealing with secondary rate limits</a>\" for details.</p>",
     "bodyParameters": [
       {
         "type": "string",
diff --git a/lib/rest/static/dereferenced/api.github.com.deref.json b/lib/rest/static/dereferenced/api.github.com.deref.json
index d1470eea15..02ff05a921 100644
--- a/lib/rest/static/dereferenced/api.github.com.deref.json
+++ b/lib/rest/static/dereferenced/api.github.com.deref.json
@@ -25663,9 +25663,6 @@
         "x-github": {
           "githubCloudOnly": false,
           "enabledForGitHubApps": false,
-          "previews": [
-
-          ],
           "category": "enterprise-admin",
           "subcategory": "billing"
         }
@@ -54415,9 +54412,6 @@
         "x-github": {
           "githubCloudOnly": true,
           "enabledForGitHubApps": true,
-          "previews": [
-
-          ],
           "category": "teams",
           "subcategory": "external-groups"
         }
@@ -102802,9 +102796,6 @@
         "x-github": {
           "githubCloudOnly": false,
           "enabledForGitHubApps": true,
-          "previews": [
-
-          ],
           "category": "billing",
           "subcategory": null
         }
@@ -254328,7 +254319,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -279040,7 +279031,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/rest/static/dereferenced/ghes-3.0.deref.json b/lib/rest/static/dereferenced/ghes-3.0.deref.json
index 3911303cb9..8abfabcccb 100644
--- a/lib/rest/static/dereferenced/ghes-3.0.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.0.deref.json
@@ -206456,7 +206456,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -231159,7 +231159,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.0/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.0/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/rest/static/dereferenced/ghes-3.1.deref.json b/lib/rest/static/dereferenced/ghes-3.1.deref.json
index f8836a617d..c7c2038031 100644
--- a/lib/rest/static/dereferenced/ghes-3.1.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.1.deref.json
@@ -209445,7 +209445,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -234148,7 +234148,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.1/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.1/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/rest/static/dereferenced/ghes-3.2.deref.json b/lib/rest/static/dereferenced/ghes-3.2.deref.json
index 4774fab2f8..e04292b656 100644
--- a/lib/rest/static/dereferenced/ghes-3.2.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.2.deref.json
@@ -216117,7 +216117,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -240883,7 +240883,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.2/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.2/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/rest/static/dereferenced/ghes-3.3.deref.json b/lib/rest/static/dereferenced/ghes-3.3.deref.json
index a32b2b1779..6f085c4d09 100644
--- a/lib/rest/static/dereferenced/ghes-3.3.deref.json
+++ b/lib/rest/static/dereferenced/ghes-3.3.deref.json
@@ -223073,7 +223073,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -247785,7 +247785,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/enterprise-server@3.3/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/enterprise-server@3.3/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/rest/static/dereferenced/github.ae.deref.json b/lib/rest/static/dereferenced/github.ae.deref.json
index f6907c33e6..a63ed2f839 100644
--- a/lib/rest/static/dereferenced/github.ae.deref.json
+++ b/lib/rest/static/dereferenced/github.ae.deref.json
@@ -35909,9 +35909,6 @@
         "x-github": {
           "githubCloudOnly": true,
           "enabledForGitHubApps": true,
-          "previews": [
-
-          ],
           "category": "teams",
           "subcategory": "external-groups"
         }
@@ -185066,7 +185063,7 @@
       },
       "post": {
         "summary": "Create an issue",
-        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "Any user with pull access to a repository can create an issue. If [issues are disabled in the repository](https://help.github.com/articles/disabling-issues/), the API returns a `410 Gone` status.\n\nThis endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
@@ -209778,7 +209775,7 @@
       },
       "post": {
         "summary": "Create an issue comment",
-        "description": "This endpoint triggers [notifications](https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
+        "description": "This endpoint triggers [notifications](https://docs.github.com/github-ae@latest/github/managing-subscriptions-and-notifications-on-github/about-notifications). Creating content too quickly using this endpoint may result in secondary rate limiting. See \"[Secondary rate limits](https://docs.github.com/github-ae@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits)\" and \"[Dealing with secondary rate limits](https://docs.github.com/github-ae@latest/rest/guides/best-practices-for-integrators#dealing-with-secondary-rate-limits)\" for details.",
         "tags": [
           "issues"
         ],
diff --git a/lib/search/indexes/github-docs-3.0-cn-records.json.br b/lib/search/indexes/github-docs-3.0-cn-records.json.br
index 4aea1cc1b5..a23bb743e6 100644
--- a/lib/search/indexes/github-docs-3.0-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9fcbe8db5ac16bb4998c92738763c294c4787c06d5ebde088faca54f236ec3a3
-size 648008
+oid sha256:284e2310f5ea3e80bd5e11386a214bfaa351f14b6cd5d19ceaedc9e596cfed9d
+size 651801
diff --git a/lib/search/indexes/github-docs-3.0-cn.json.br b/lib/search/indexes/github-docs-3.0-cn.json.br
index 7173ee2bdb..aa5cea2680 100644
--- a/lib/search/indexes/github-docs-3.0-cn.json.br
+++ b/lib/search/indexes/github-docs-3.0-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:fb6e403006ca552fc906153f5046191c2666ba74b49c9762db48f3b0782ece9f
-size 1353332
+oid sha256:fd9e3dab547dfb8b916bca2aa652065b0abe54b9d9d438a8fd51437ac65b47ba
+size 1367087
diff --git a/lib/search/indexes/github-docs-3.0-en-records.json.br b/lib/search/indexes/github-docs-3.0-en-records.json.br
index 0013d18296..2243059e15 100644
--- a/lib/search/indexes/github-docs-3.0-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:915865176744e420773e6e8046909ead65f5650360112d6a2279968dab998b99
-size 967118
+oid sha256:ae02c7fe62ffd750c7af187d19394948aad2a32a30ecfbe479521a829757fca0
+size 966876
diff --git a/lib/search/indexes/github-docs-3.0-en.json.br b/lib/search/indexes/github-docs-3.0-en.json.br
index 823af50615..fd36e0dc6a 100644
--- a/lib/search/indexes/github-docs-3.0-en.json.br
+++ b/lib/search/indexes/github-docs-3.0-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9b160d1d656e22d047f1af3c406601c495347ca6bd95699f480cb846a6cc7a49
-size 3963925
+oid sha256:edce77d8545918d48608761c9fc485bb1583830ff1551200c4d8103e6348e089
+size 3965279
diff --git a/lib/search/indexes/github-docs-3.0-es-records.json.br b/lib/search/indexes/github-docs-3.0-es-records.json.br
index 203900dda0..911e60ea35 100644
--- a/lib/search/indexes/github-docs-3.0-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:09a5ba768bb0dbfb43e41f827f834c4b5ae158cb3accbe6e696172306a530aae
-size 603209
+oid sha256:b27eed498387d38a7cdc55be915bf24bf3eb03a855f4f2ccf22eebd15f9ce5e5
+size 606807
diff --git a/lib/search/indexes/github-docs-3.0-es.json.br b/lib/search/indexes/github-docs-3.0-es.json.br
index e21644b457..bc1996f6e9 100644
--- a/lib/search/indexes/github-docs-3.0-es.json.br
+++ b/lib/search/indexes/github-docs-3.0-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:928ee28e3e0577858c6c95be82f7c83a62ac9e38b2802bedc574e31f4b4f78d2
-size 2543729
+oid sha256:392c8529e2c8f1ecf80f504de15d9e815010e1c2f92138502f21899e1c760ad2
+size 2561474
diff --git a/lib/search/indexes/github-docs-3.0-ja-records.json.br b/lib/search/indexes/github-docs-3.0-ja-records.json.br
index f105a6b7d6..8e7073cab9 100644
--- a/lib/search/indexes/github-docs-3.0-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1fe222fc01f0838ff085815a39945b48695dc7c9596314357102c9c8bd421370
-size 666961
+oid sha256:6f9cbf7e403865cc08c2c98cd03d4f50b90988937a9d7ad4177a8f1a3aa6aaed
+size 670613
diff --git a/lib/search/indexes/github-docs-3.0-ja.json.br b/lib/search/indexes/github-docs-3.0-ja.json.br
index fdbb2840c1..e9f632133e 100644
--- a/lib/search/indexes/github-docs-3.0-ja.json.br
+++ b/lib/search/indexes/github-docs-3.0-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:16c0a8ac43b391da60a38810b8d5e5a44779e66ab0ef83b9ea89c60fc99d4c35
-size 3554134
+oid sha256:415ec882844877c6ce5922c46afa50425189b2e0db4ee52c89bd33a0b05d9f56
+size 3578306
diff --git a/lib/search/indexes/github-docs-3.0-pt-records.json.br b/lib/search/indexes/github-docs-3.0-pt-records.json.br
index 3c6ed17045..b1c051ad9d 100644
--- a/lib/search/indexes/github-docs-3.0-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0240fb39332aad8b932be331182a39a1a3061110a6eedfd7bfe58dba0384eb73
-size 592770
+oid sha256:5e1bbe452ddc1b723a3163857ac7f348f58f7813dbee0f31f95127fde974ab56
+size 596731
diff --git a/lib/search/indexes/github-docs-3.0-pt.json.br b/lib/search/indexes/github-docs-3.0-pt.json.br
index 12989facea..6b064dfd82 100644
--- a/lib/search/indexes/github-docs-3.0-pt.json.br
+++ b/lib/search/indexes/github-docs-3.0-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c6c72013635966e549b32933a6a4a443e3fc8dab8d8f5bb2321885ba31830a0b
-size 2433314
+oid sha256:8026fa6823602535a49fbf7ac761add2dac16e227403af868270f2410e4fd3ea
+size 2456148
diff --git a/lib/search/indexes/github-docs-3.1-cn-records.json.br b/lib/search/indexes/github-docs-3.1-cn-records.json.br
index be3c4f7bf6..7a0c63ca91 100644
--- a/lib/search/indexes/github-docs-3.1-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4552e0fc400ff23a22d6b8e112189551b758413580826c12ee4f01b351f2b49d
-size 662417
+oid sha256:961263562aab594e5fea1216ded9d8ec6ac0aeb6735b85f16f60440f5b6ba720
+size 666053
diff --git a/lib/search/indexes/github-docs-3.1-cn.json.br b/lib/search/indexes/github-docs-3.1-cn.json.br
index c5f12e4034..bd374437e9 100644
--- a/lib/search/indexes/github-docs-3.1-cn.json.br
+++ b/lib/search/indexes/github-docs-3.1-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:fdf06ed40911a631ee2f01ee22918333e208f47ecf2a1b458be76c5299553dd0
-size 1391809
+oid sha256:dfd322f22757ed1902539e5d6a116bef911ba108cb0e59ce8152e56e0aec689f
+size 1406321
diff --git a/lib/search/indexes/github-docs-3.1-en-records.json.br b/lib/search/indexes/github-docs-3.1-en-records.json.br
index 28e66020a7..47f2d3c0a0 100644
--- a/lib/search/indexes/github-docs-3.1-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d38b2ee1470982034bc625f5171b58dceb4e4234857387487f1034713ac4f847
-size 991256
+oid sha256:8bbf1859bdd143d4f707e3c31ab8367e29554850857f33b8bb2bf838782f90a1
+size 994912
diff --git a/lib/search/indexes/github-docs-3.1-en.json.br b/lib/search/indexes/github-docs-3.1-en.json.br
index e43630073d..fcede91dc4 100644
--- a/lib/search/indexes/github-docs-3.1-en.json.br
+++ b/lib/search/indexes/github-docs-3.1-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5bbf4d15d86594754bf5ae3ce067c746fa4a9305234d2520daa9822ed50c6efa
-size 4057787
+oid sha256:e425b6e1fffc38b0616cfef81a10659d2e84a6afaca7e1d5ca0a128c25130d7f
+size 4057834
diff --git a/lib/search/indexes/github-docs-3.1-es-records.json.br b/lib/search/indexes/github-docs-3.1-es-records.json.br
index 63c1ff28d7..8e85b49cd9 100644
--- a/lib/search/indexes/github-docs-3.1-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:314650af5ca61c5a6928aa192b2940356a4e44c849bdd8e14fac4900e9acd74a
-size 615704
+oid sha256:b77f0b0623d813d0636df9db46d40b4b953553e8d164956a7d9c2210428a7057
+size 619327
diff --git a/lib/search/indexes/github-docs-3.1-es.json.br b/lib/search/indexes/github-docs-3.1-es.json.br
index a7b69c0e48..5a0b6b7340 100644
--- a/lib/search/indexes/github-docs-3.1-es.json.br
+++ b/lib/search/indexes/github-docs-3.1-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:47b53b466b4faaca0cdad3806831a235a5a23c3880d2c24fdf3937e2601e5bfb
-size 2605266
+oid sha256:d494241f6e757fa85af674f1a52e7c82e3efa9312642f247a662b2e64e08b31b
+size 2623960
diff --git a/lib/search/indexes/github-docs-3.1-ja-records.json.br b/lib/search/indexes/github-docs-3.1-ja-records.json.br
index 277ad103e9..08beb015c2 100644
--- a/lib/search/indexes/github-docs-3.1-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:0c205c6db1a086819e247c85d647a4c0b5df8d122d79bc9ee61ab89fd360f0e0
-size 681539
+oid sha256:51088bce022461ff17d7513267ed97a11f9f0d2930bbe9a8867f4d0d4e365aa7
+size 684945
diff --git a/lib/search/indexes/github-docs-3.1-ja.json.br b/lib/search/indexes/github-docs-3.1-ja.json.br
index a78ececdc5..ee60ec24cd 100644
--- a/lib/search/indexes/github-docs-3.1-ja.json.br
+++ b/lib/search/indexes/github-docs-3.1-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:fbca128740dca9197786aff57cefc112a3d856dddefe23dd3121478fb9dd0061
-size 3635650
+oid sha256:0c18396d7d9a41f5b28ad9f582567b5998a7a9e8be7419eb0744be99d6735c4d
+size 3661220
diff --git a/lib/search/indexes/github-docs-3.1-pt-records.json.br b/lib/search/indexes/github-docs-3.1-pt-records.json.br
index d563219312..fba79453d5 100644
--- a/lib/search/indexes/github-docs-3.1-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e74c2f19c0e012e0db96c86b783778304c6e23037b98f68150fa1d8985d2b01a
-size 605328
+oid sha256:430ecf42bd2c2694b137a1cc559a6011089538cd6df52b3fd718de7175b4a2eb
+size 609131
diff --git a/lib/search/indexes/github-docs-3.1-pt.json.br b/lib/search/indexes/github-docs-3.1-pt.json.br
index 2fa5a2b1b1..cf1556c755 100644
--- a/lib/search/indexes/github-docs-3.1-pt.json.br
+++ b/lib/search/indexes/github-docs-3.1-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:d3bc18ac8f71112a1d01f6366f0a8b4e02543e1d0a2ed7a7d84aa8bc370b7ea9
-size 2488203
+oid sha256:f7e952874e3e790b2197c6414d090fbc8455c3b7a598e8cfab607ee90db5902a
+size 2510096
diff --git a/lib/search/indexes/github-docs-3.2-cn-records.json.br b/lib/search/indexes/github-docs-3.2-cn-records.json.br
index 8de1408f87..80b7fe5cfb 100644
--- a/lib/search/indexes/github-docs-3.2-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2e8a0bc46d3bf3c9596bc8d84af9aef6ac811306772705b6358f36f94fdba50a
-size 676509
+oid sha256:29ff98dc6cbbb90803ee30c36b2c01f2902857acc5779092b95ce7b05038e2a4
+size 680532
diff --git a/lib/search/indexes/github-docs-3.2-cn.json.br b/lib/search/indexes/github-docs-3.2-cn.json.br
index 1820ba8b6b..38ad47642d 100644
--- a/lib/search/indexes/github-docs-3.2-cn.json.br
+++ b/lib/search/indexes/github-docs-3.2-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e7d7058321f5b2586d100a57e260014eb541f0a2b32e720f52eaf1d8baf1c8b5
-size 1419887
+oid sha256:03d898d117a57936313e77a7a55918e051b7cc03dc135deb68d7e19ad606bf51
+size 1434349
diff --git a/lib/search/indexes/github-docs-3.2-en-records.json.br b/lib/search/indexes/github-docs-3.2-en-records.json.br
index eccef57f13..802a418652 100644
--- a/lib/search/indexes/github-docs-3.2-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:cb5d6b95467b98baa323066ad5838b860a43581cc83d925fa75251b32c3e1c31
-size 1024366
+oid sha256:53ea02905c70568d26fa1d7ae2b9f8dd36096fd67a4ea285844ebfdb55472dab
+size 1024350
diff --git a/lib/search/indexes/github-docs-3.2-en.json.br b/lib/search/indexes/github-docs-3.2-en.json.br
index 9f755fbb94..323fc0d44e 100644
--- a/lib/search/indexes/github-docs-3.2-en.json.br
+++ b/lib/search/indexes/github-docs-3.2-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:54f5a73c78becdec45634557a4029797ebe6e19f1613cd9a848b40e174f8193f
-size 4189223
+oid sha256:fbd4841c5624cd7aac05150ec37ead3133d38600acca13c4680fbe6d394f1cde
+size 4189425
diff --git a/lib/search/indexes/github-docs-3.2-es-records.json.br b/lib/search/indexes/github-docs-3.2-es-records.json.br
index 9facb8f608..f8224a3c9b 100644
--- a/lib/search/indexes/github-docs-3.2-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6c33c1d9224b6196e1b84f598cdf37137f39b78af24341dd0b1555b61d9d8975
-size 628945
+oid sha256:dec86a801007b50e16a198793f45dd4c9842c419a3347882b84c15d7deb42c02
+size 632897
diff --git a/lib/search/indexes/github-docs-3.2-es.json.br b/lib/search/indexes/github-docs-3.2-es.json.br
index a170861e0d..2a5a461694 100644
--- a/lib/search/indexes/github-docs-3.2-es.json.br
+++ b/lib/search/indexes/github-docs-3.2-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:43d79987fa35238adc831c7d355e67decc9977665dbe3d10082de68c841796b4
-size 2663805
+oid sha256:98f774ab36aa5de7fb5323120b008d1b15b199a5d56e903983902cf20fe0fb72
+size 2683517
diff --git a/lib/search/indexes/github-docs-3.2-ja-records.json.br b/lib/search/indexes/github-docs-3.2-ja-records.json.br
index c556ac1f80..113c940289 100644
--- a/lib/search/indexes/github-docs-3.2-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:cec68771c444af7a0e37c67259e2c708b76514b6cf12f11841951616652419a6
-size 694275
+oid sha256:44c14ba35f8be27bf8128965c507b28bb640a77d4ede0c8b4148fbebc364cd31
+size 697732
diff --git a/lib/search/indexes/github-docs-3.2-ja.json.br b/lib/search/indexes/github-docs-3.2-ja.json.br
index 183d5fc1a0..0fb71c11a2 100644
--- a/lib/search/indexes/github-docs-3.2-ja.json.br
+++ b/lib/search/indexes/github-docs-3.2-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3247f67093f91458dbff2947a5e87ddcfdc6b5f51364a3bf4f80beeb1702daac
-size 3713826
+oid sha256:9aefe23354f40ee6b051b6fb2de6f511bcdc357ed1fa7245b0385d886eac4190
+size 3738229
diff --git a/lib/search/indexes/github-docs-3.2-pt-records.json.br b/lib/search/indexes/github-docs-3.2-pt-records.json.br
index b34b31c869..63e7cd4b68 100644
--- a/lib/search/indexes/github-docs-3.2-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4c535a246c781382628fff08c9c56a6082edc349cc7e67f59ce7377a71843582
-size 618219
+oid sha256:7cb6d540d2ea5760cfdf285f9096eeae458ec1f57cc5052da99bae4b623164dd
+size 621836
diff --git a/lib/search/indexes/github-docs-3.2-pt.json.br b/lib/search/indexes/github-docs-3.2-pt.json.br
index f116acea90..21dabad6bf 100644
--- a/lib/search/indexes/github-docs-3.2-pt.json.br
+++ b/lib/search/indexes/github-docs-3.2-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9e41bd93f516fbe5775a38345a1824691f03c172619c3e3ded8e2a7e11644d28
-size 2540879
+oid sha256:8b3fe0bb5266a1cf0a4e0e63e73b8bd1c1c63357a43c375a2a7700a5b26323ee
+size 2563977
diff --git a/lib/search/indexes/github-docs-3.3-cn-records.json.br b/lib/search/indexes/github-docs-3.3-cn-records.json.br
index 4221e6423d..3eacf88bd1 100644
--- a/lib/search/indexes/github-docs-3.3-cn-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:7293211234925d6b8269d5b4e549436e5dccb04a1378425e40825c9aad024706
-size 699028
+oid sha256:c58b51aa04b37cde74f139473f0882ad6bc833a21f7bbb3ca0ad927ea778d5da
+size 702431
diff --git a/lib/search/indexes/github-docs-3.3-cn.json.br b/lib/search/indexes/github-docs-3.3-cn.json.br
index 371a9f0bcb..442f4c1928 100644
--- a/lib/search/indexes/github-docs-3.3-cn.json.br
+++ b/lib/search/indexes/github-docs-3.3-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:3d25234e26f2c4482237f454e1cb0646582e43279c54cb6e2efb5f4d834559fa
-size 1478380
+oid sha256:e229348b75dd60f52d6770e78929bed0c83fe8625fb6d762f41e10c5272e5910
+size 1492477
diff --git a/lib/search/indexes/github-docs-3.3-en-records.json.br b/lib/search/indexes/github-docs-3.3-en-records.json.br
index a8a487be9d..9c12139323 100644
--- a/lib/search/indexes/github-docs-3.3-en-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bc280117f4c78fb83ae949767cf150249f964cec0fb75eaf709777d64155c688
-size 1058674
+oid sha256:ac48f80fbfd4a3c96be6b1cf4de7fca3e7d0a7602e08cc4ca8d7a44d6f84ea6a
+size 1058321
diff --git a/lib/search/indexes/github-docs-3.3-en.json.br b/lib/search/indexes/github-docs-3.3-en.json.br
index 3a5a432394..715a874b13 100644
--- a/lib/search/indexes/github-docs-3.3-en.json.br
+++ b/lib/search/indexes/github-docs-3.3-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:bbca917ab3fd986111ade1111e3a11f65b064a86b7d3b7671a23e04b2d4a5907
-size 4290143
+oid sha256:432e5c3ce5aee49305535a76b0fd7925ac8ab660632ecdf980da19736b88e79a
+size 4289534
diff --git a/lib/search/indexes/github-docs-3.3-es-records.json.br b/lib/search/indexes/github-docs-3.3-es-records.json.br
index e0f80afa3b..baa8e8ad40 100644
--- a/lib/search/indexes/github-docs-3.3-es-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be413a0fedaae3aa1188a94d9276bbf341f87f121b76f13c703fbc7e786089a2
-size 647717
+oid sha256:671d0d0310c27ad62eeeeb5ac7ce3d4024c107a182b5b35486f1a6e3a1334354
+size 651462
diff --git a/lib/search/indexes/github-docs-3.3-es.json.br b/lib/search/indexes/github-docs-3.3-es.json.br
index 469b172b94..7a0ad081cc 100644
--- a/lib/search/indexes/github-docs-3.3-es.json.br
+++ b/lib/search/indexes/github-docs-3.3-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:dfa36442c488c8c7904485f5ee62b42b3af424d08087b3d1edf70eee1420be20
-size 2763268
+oid sha256:e27ac5ea080125b1166edfc5eac437d3c1bbfe2e048f38ac55d26b76ddf7155e
+size 2782749
diff --git a/lib/search/indexes/github-docs-3.3-ja-records.json.br b/lib/search/indexes/github-docs-3.3-ja-records.json.br
index 0c2175b2e1..4caf82b5bb 100644
--- a/lib/search/indexes/github-docs-3.3-ja-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:de57eb848b26daa8a6dec1c275b0fa678fa5e58db7f576b7cd51494f429d0b8e
-size 716625
+oid sha256:72d87e6318b1cb5e208e1a464cac6bf8644f07c36e084d63da4a0ca6465fc80f
+size 720580
diff --git a/lib/search/indexes/github-docs-3.3-ja.json.br b/lib/search/indexes/github-docs-3.3-ja.json.br
index d0a9f74091..a66a2e3ef0 100644
--- a/lib/search/indexes/github-docs-3.3-ja.json.br
+++ b/lib/search/indexes/github-docs-3.3-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:ccd05d598ea6b372aa2ccaeb904ba04bbeacd84f608565b9c747bfc31c0260ea
-size 3838052
+oid sha256:2032f768056d6fb22dcfe083943150a907a6beb78587f67e1ef862fb5a0c1d67
+size 3864410
diff --git a/lib/search/indexes/github-docs-3.3-pt-records.json.br b/lib/search/indexes/github-docs-3.3-pt-records.json.br
index aec981aba3..867a87f01e 100644
--- a/lib/search/indexes/github-docs-3.3-pt-records.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:951bfeb43f2c138671ff96777a4d1553ebe394613bf011fd8f3fc45870aace70
-size 636705
+oid sha256:e256b8ed26c572607c4edb2e42cb421404dc0bee9f1e69ec226567c386336bd5
+size 640550
diff --git a/lib/search/indexes/github-docs-3.3-pt.json.br b/lib/search/indexes/github-docs-3.3-pt.json.br
index d1942e41a6..e717fcbfe1 100644
--- a/lib/search/indexes/github-docs-3.3-pt.json.br
+++ b/lib/search/indexes/github-docs-3.3-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f4b2660dd768f10516478fb4f5085c181c8f430032dacaa9bc0c89c0a6a3a531
-size 2621201
+oid sha256:f6da09246a31e6e7b5490c0abcf66f267a2127adb641c90497948aea054ec9dd
+size 2643995
diff --git a/lib/search/indexes/github-docs-dotcom-cn-records.json.br b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
index ab642b66ef..e908be53a6 100644
--- a/lib/search/indexes/github-docs-dotcom-cn-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a2c015657a56c56c736f9e0e938cc81fc752c4c95c033470fff4e0a06c989cf9
-size 901415
+oid sha256:67b775ba69f554319d019c3df9cfa5d9d093e2f4d2ddb7b1dc266c11120bbd40
+size 901604
diff --git a/lib/search/indexes/github-docs-dotcom-cn.json.br b/lib/search/indexes/github-docs-dotcom-cn.json.br
index 0d17da4ea5..df313015eb 100644
--- a/lib/search/indexes/github-docs-dotcom-cn.json.br
+++ b/lib/search/indexes/github-docs-dotcom-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:fd4aa6817a5a52f32165e8938b2f352dc46ee640477e0d2e2508650d89d77cee
-size 1661267
+oid sha256:6cac4a8027d0548a48c5ead525bc137ee6bb56bce230b2739e41093c3733225f
+size 1661906
diff --git a/lib/search/indexes/github-docs-dotcom-en-records.json.br b/lib/search/indexes/github-docs-dotcom-en-records.json.br
index 6e073d8d1f..f5bf3807e8 100644
--- a/lib/search/indexes/github-docs-dotcom-en-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5a18bf20ec4c6ee2cd1ac2f72e7b7557b746fe561ac97306302636e862003671
-size 1342236
+oid sha256:9eb5284c3a85a9baabe769b832b4216dcab7fd2f362a9f0659e741ee2ac69ee7
+size 1341949
diff --git a/lib/search/indexes/github-docs-dotcom-en.json.br b/lib/search/indexes/github-docs-dotcom-en.json.br
index 2ef299c3a5..b7619df92e 100644
--- a/lib/search/indexes/github-docs-dotcom-en.json.br
+++ b/lib/search/indexes/github-docs-dotcom-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:1c403c9a4098336cac84bcf4662df86272279976e164a706a3b145aacf2e930d
-size 5155064
+oid sha256:0135fe5d6b3d8346a736c344c6783891421663cde4f5710c5a4f6fa6bb4be66f
+size 5155619
diff --git a/lib/search/indexes/github-docs-dotcom-es-records.json.br b/lib/search/indexes/github-docs-dotcom-es-records.json.br
index 7bf655d117..282ed6902b 100644
--- a/lib/search/indexes/github-docs-dotcom-es-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:be22fb3a7088490c4a6e068fccbff50a2293a83656cd48e6c53b832e88891a64
-size 819211
+oid sha256:d52f8a82dba19d117224fc7a287ecb197c2ea8230a57045105682d7ebedaf776
+size 819297
diff --git a/lib/search/indexes/github-docs-dotcom-es.json.br b/lib/search/indexes/github-docs-dotcom-es.json.br
index 32dad16247..4bd2c9a523 100644
--- a/lib/search/indexes/github-docs-dotcom-es.json.br
+++ b/lib/search/indexes/github-docs-dotcom-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:8d815a1a5a436f0c954de46980acf99f0e54eec645f63fa4cb573c6b11b2bc82
-size 3319529
+oid sha256:51ed4c0030927708b947879bdb49e00f5da2cd97a8cd61dd7aa3caaf78de28ce
+size 3320198
diff --git a/lib/search/indexes/github-docs-dotcom-ja-records.json.br b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
index 76a7bd36d8..55ae0447d1 100644
--- a/lib/search/indexes/github-docs-dotcom-ja-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:89ceb9f14dcc8a244a65740527f7e75b8c87e060642727d7a667252111321f8d
-size 919218
+oid sha256:e65632fa7799368c261ac864eb3e615ee2e095da8678107351e6fecdf4e63d17
+size 919287
diff --git a/lib/search/indexes/github-docs-dotcom-ja.json.br b/lib/search/indexes/github-docs-dotcom-ja.json.br
index 302420cb10..49a24e5a93 100644
--- a/lib/search/indexes/github-docs-dotcom-ja.json.br
+++ b/lib/search/indexes/github-docs-dotcom-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:c08ec60e1abf921fc96de070d14c615849f67c86b39ba99bc13e10f6391dadad
-size 4715440
+oid sha256:557826d22bbc9c4b0cb00b0d62a5d48423f5c871743b04c873907cac36036e7d
+size 4715420
diff --git a/lib/search/indexes/github-docs-dotcom-pt-records.json.br b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
index ccdfce0ce3..41a1fb3841 100644
--- a/lib/search/indexes/github-docs-dotcom-pt-records.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4c2ca30428477e201c5fadf8e12da74f2d393483269a83147ce79df23749b52e
-size 808358
+oid sha256:2e431b98594349e58348099fdba2ead54509597ead6ca450c60a6b4490cb84f1
+size 808337
diff --git a/lib/search/indexes/github-docs-dotcom-pt.json.br b/lib/search/indexes/github-docs-dotcom-pt.json.br
index b6661a5629..df38c26831 100644
--- a/lib/search/indexes/github-docs-dotcom-pt.json.br
+++ b/lib/search/indexes/github-docs-dotcom-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:166418ad1d59b99a10e0040ac11d59b0e5d59078f65364ae156acd5e36e28829
-size 3169959
+oid sha256:57040da2e87bcb14565467b4f2e07ed18419219309f9406f5b932910cf758e78
+size 3168150
diff --git a/lib/search/indexes/github-docs-ghae-cn-records.json.br b/lib/search/indexes/github-docs-ghae-cn-records.json.br
index 855d78e576..894096591c 100644
--- a/lib/search/indexes/github-docs-ghae-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:77182a8bb9ce03b37223fec82c8cab8801540eee862b81ec13964d3525f265b0
-size 545242
+oid sha256:7df36077055799d913fed388005d8611f57869075f56016140894b934ec39f9a
+size 547902
diff --git a/lib/search/indexes/github-docs-ghae-cn.json.br b/lib/search/indexes/github-docs-ghae-cn.json.br
index 55aa326584..1ad8cb812e 100644
--- a/lib/search/indexes/github-docs-ghae-cn.json.br
+++ b/lib/search/indexes/github-docs-ghae-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:689db9b654d365045ed6edb984fce7bd7f45004eb433fade1b0249fc9ecc3038
-size 1101778
+oid sha256:98f78aa61ffc198d0521e82f52ba7f7703bdd8567cf70489acab0dc70c864332
+size 1111544
diff --git a/lib/search/indexes/github-docs-ghae-en-records.json.br b/lib/search/indexes/github-docs-ghae-en-records.json.br
index f12a4f1bb7..0c676a39f2 100644
--- a/lib/search/indexes/github-docs-ghae-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e1fb5c00992d938aee7ad5d80a99450b4646102e2728b6163172b7ad246e148f
-size 843755
+oid sha256:921c5408e7648c41d7dd310731a469f405fd8ed0ecc745a8fe7029a527d2475d
+size 844007
diff --git a/lib/search/indexes/github-docs-ghae-en.json.br b/lib/search/indexes/github-docs-ghae-en.json.br
index 5c66193fc0..eca38cd715 100644
--- a/lib/search/indexes/github-docs-ghae-en.json.br
+++ b/lib/search/indexes/github-docs-ghae-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:38a0f5070b5c9f244c0d942fdf3edc82d88695d96ed747f08aacb00f6e944968
-size 3398360
+oid sha256:48c7bc5b51b2de557e85644aafba4d4fd7d293642b6131a67afb725c010079bf
+size 3397900
diff --git a/lib/search/indexes/github-docs-ghae-es-records.json.br b/lib/search/indexes/github-docs-ghae-es-records.json.br
index a9e513caee..4b9e3a3c0f 100644
--- a/lib/search/indexes/github-docs-ghae-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5c0c730cd2e671127712e3d5d5e35e4639a41f414da2932cc29482b2d2dedc6e
-size 507262
+oid sha256:054f425bc793187faeca097255abd4f361ba5a88460ef33ecfb90499e6571cb0
+size 510116
diff --git a/lib/search/indexes/github-docs-ghae-es.json.br b/lib/search/indexes/github-docs-ghae-es.json.br
index 840f00e7f1..b9e3af8abb 100644
--- a/lib/search/indexes/github-docs-ghae-es.json.br
+++ b/lib/search/indexes/github-docs-ghae-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5b2cdd2c8a77f4b1cec696978ea515735612f0e26e461174444c2a110726019d
-size 2079039
+oid sha256:fe838baa751ac5fd426c4952eeaefd69ae617551d4102e4cee83a0e04700cc55
+size 2093478
diff --git a/lib/search/indexes/github-docs-ghae-ja-records.json.br b/lib/search/indexes/github-docs-ghae-ja-records.json.br
index 574712bc48..e0e51555cd 100644
--- a/lib/search/indexes/github-docs-ghae-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:878c43795016bc97827e01cfdbc9afe0a44c9160a963f6c63784be53061ef3d8
-size 558294
+oid sha256:25db4c28bb585365a357d7e228979ec61c92dda956751db8643a35119fe71244
+size 560931
diff --git a/lib/search/indexes/github-docs-ghae-ja.json.br b/lib/search/indexes/github-docs-ghae-ja.json.br
index 384d7292a5..d6faa14758 100644
--- a/lib/search/indexes/github-docs-ghae-ja.json.br
+++ b/lib/search/indexes/github-docs-ghae-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:f8cc16414684d285637888bd68975c6be627cb32e8aeae4609e8d669076f5b58
-size 2879854
+oid sha256:6f6e0cb0322a40a8204a97dea0ebf8c810e1ea2f5f453ba94e2df6cbac1a5de1
+size 2896689
diff --git a/lib/search/indexes/github-docs-ghae-pt-records.json.br b/lib/search/indexes/github-docs-ghae-pt-records.json.br
index b159779a67..e4b9546e6d 100644
--- a/lib/search/indexes/github-docs-ghae-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6c1ae3a5e2e8fbadd78d322c29705673cac2498ff58807a2241dbbc886970109
-size 499330
+oid sha256:e62f8c1cb1e8f8d6d38baf0c0c45b3d547994d47809f482221aa973d202827b2
+size 502036
diff --git a/lib/search/indexes/github-docs-ghae-pt.json.br b/lib/search/indexes/github-docs-ghae-pt.json.br
index 4f298562a5..25f9f28876 100644
--- a/lib/search/indexes/github-docs-ghae-pt.json.br
+++ b/lib/search/indexes/github-docs-ghae-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:96c41836bb67d84af576a77af152f1ad1db59a955f7f2b5b3682e729ab646fbf
-size 1967922
+oid sha256:bf7cf4e5c45d1970a5800f7fdb370a9f906ac0d85ff79df3f9ccbf062f225932
+size 1984084
diff --git a/lib/search/indexes/github-docs-ghec-cn-records.json.br b/lib/search/indexes/github-docs-ghec-cn-records.json.br
index c3352ebc3c..5f3495f2f4 100644
--- a/lib/search/indexes/github-docs-ghec-cn-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:2e301c596eec60bb4e1c66906c3c350d07799f1d297387cf0c5d2106c9257f3a
-size 822630
+oid sha256:f0bcda551d3da453b9934619f6f4b724fc9a6407a1d2ba86e6866b454e469661
+size 823005
diff --git a/lib/search/indexes/github-docs-ghec-cn.json.br b/lib/search/indexes/github-docs-ghec-cn.json.br
index 7a37d26b8c..0572e451f8 100644
--- a/lib/search/indexes/github-docs-ghec-cn.json.br
+++ b/lib/search/indexes/github-docs-ghec-cn.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9935be5b72a035d72bc62e0475e81fc729b2ce14ccd08b34e870ef7d672722a2
-size 1707377
+oid sha256:acc34064a5b8003129109f27efdf6e2c18ca0ab67c5e9d787e189feeac0bdb87
+size 1710403
diff --git a/lib/search/indexes/github-docs-ghec-en-records.json.br b/lib/search/indexes/github-docs-ghec-en-records.json.br
index 9a709856df..cbea68326c 100644
--- a/lib/search/indexes/github-docs-ghec-en-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-en-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:a89ca2c676c1ca8175c08f4b5f2f9d168ccb50214954b23437da8c082314d47c
-size 1212390
+oid sha256:7de57f73f0bbc063239e1872213ba5d66ccf337891a8e4728f10d22d2f092a38
+size 1212370
diff --git a/lib/search/indexes/github-docs-ghec-en.json.br b/lib/search/indexes/github-docs-ghec-en.json.br
index 7e175fa0ed..ee91363ce8 100644
--- a/lib/search/indexes/github-docs-ghec-en.json.br
+++ b/lib/search/indexes/github-docs-ghec-en.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:abfddc0f83612a9cd71959645e53f46f799e8d97363a9b4f0260800010decfb3
-size 4911646
+oid sha256:6a402e3ee34c1baba27892cd8e5f84d5bee8f66357968a441233ad6fa46a5dac
+size 4912416
diff --git a/lib/search/indexes/github-docs-ghec-es-records.json.br b/lib/search/indexes/github-docs-ghec-es-records.json.br
index ce618e4c6f..e111ecb3a3 100644
--- a/lib/search/indexes/github-docs-ghec-es-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-es-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:9fdec3fab2d7daca3cbb8cbb170cef0f1dbfa0baaeb67abed5ba419700c25548
-size 772750
+oid sha256:808b9e5cfb3601df566f880e4cb69e3b757a7c0a467352e457e220ca6aec8e48
+size 773026
diff --git a/lib/search/indexes/github-docs-ghec-es.json.br b/lib/search/indexes/github-docs-ghec-es.json.br
index 9ffc0d16d6..103a41f8e0 100644
--- a/lib/search/indexes/github-docs-ghec-es.json.br
+++ b/lib/search/indexes/github-docs-ghec-es.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:053abdc55fa0f12ec70caf72e5137330d9200b70d343791ee68e34da70fc8f66
-size 3283749
+oid sha256:f40ec9d95e1ea2059c55120e553e964c145a45c755f5a22e7fcc91d4d2a50db4
+size 3281910
diff --git a/lib/search/indexes/github-docs-ghec-ja-records.json.br b/lib/search/indexes/github-docs-ghec-ja-records.json.br
index c57dbe8f09..31fa118fbf 100644
--- a/lib/search/indexes/github-docs-ghec-ja-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6a717217d6bcbd6385192d8584c329bcbc45ee17f1e2e1779633c6894964cfef
-size 845319
+oid sha256:a855e51caf02b7e76567868da1578bc5ce6b51f5bceedaa9be32cd560bfa2de3
+size 845268
diff --git a/lib/search/indexes/github-docs-ghec-ja.json.br b/lib/search/indexes/github-docs-ghec-ja.json.br
index 12b68a1e6b..6f6d582443 100644
--- a/lib/search/indexes/github-docs-ghec-ja.json.br
+++ b/lib/search/indexes/github-docs-ghec-ja.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:4d87a831881552f2822f995060dd0788d0db0ebeeaa53a60ad611c5e20020c95
-size 4554323
+oid sha256:0cf7eae77de9652819311678c21bbd9d53e776865af9d8fc7187299ad1857cf2
+size 4557954
diff --git a/lib/search/indexes/github-docs-ghec-pt-records.json.br b/lib/search/indexes/github-docs-ghec-pt-records.json.br
index 21549a5345..cfba0abf60 100644
--- a/lib/search/indexes/github-docs-ghec-pt-records.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt-records.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:5771eb04c934c73b279e178c229e26c28a2ea7f60c038256976448a696a8aa6d
-size 761620
+oid sha256:24727e40a4c512acbc6df64bc593c3eae6557d2e495ba261fcc1de446930bb59
+size 761781
diff --git a/lib/search/indexes/github-docs-ghec-pt.json.br b/lib/search/indexes/github-docs-ghec-pt.json.br
index eb3fc3f315..4de03dda56 100644
--- a/lib/search/indexes/github-docs-ghec-pt.json.br
+++ b/lib/search/indexes/github-docs-ghec-pt.json.br
@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:71070c34665361d8b18eadddd1f2099757a55d2586a4d7127023dd533b27d773
-size 3124715
+oid sha256:a44e93b7b9dfbdfd2d233491e9a65fd7cb2f4b39d67ab5f40b21d759c609d911
+size 3127502
diff --git a/package-lock.json b/package-lock.json
index 9e857b8278..df2b5b5ca6 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -57,7 +57,7 @@
         "mdast-util-to-string": "^3.1.0",
         "morgan": "^1.10.0",
         "next": "^11.1.3",
-        "node-fetch": "^3.1.0",
+        "node-fetch": "^3.1.1",
         "parse5": "^6.0.1",
         "port-used": "^2.0.8",
         "quick-lru": "6.0.2",
@@ -9583,9 +9583,9 @@
       }
     },
     "node_modules/fetch-blob": {
-      "version": "3.1.2",
-      "resolved": "https://registry.npmjs.org/fetch-blob/-/fetch-blob-3.1.2.tgz",
-      "integrity": "sha512-hunJbvy/6OLjCD0uuhLdp0mMPzP/yd2ssd1t2FCJsaA7wkWhpbp9xfuNVpv7Ll4jFhzp6T4LAupSiV9uOeg0VQ==",
+      "version": "3.1.4",
+      "resolved": "https://registry.npmjs.org/fetch-blob/-/fetch-blob-3.1.4.tgz",
+      "integrity": "sha512-Eq5Xv5+VlSrYWEqKrusxY1C3Hm/hjeAsCGVG3ft7pZahlUAChpGZT/Ms1WmSLnEAisEXszjzu/s+ce6HZB2VHA==",
       "funding": [
         {
           "type": "github",
@@ -9597,6 +9597,7 @@
         }
       ],
       "dependencies": {
+        "node-domexception": "^1.0.0",
         "web-streams-polyfill": "^3.0.3"
       },
       "engines": {
@@ -15903,13 +15904,31 @@
         "node": ">= 10.13"
       }
     },
+    "node_modules/node-domexception": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/node-domexception/-/node-domexception-1.0.0.tgz",
+      "integrity": "sha512-/jKZoMpw0F8GRwl4/eLROPA3cfcXtLApP0QzLmUT/HuPCZWyB7IY9ZrMeKw2O/nFIqPQB3PVM9aYm0F312AXDQ==",
+      "funding": [
+        {
+          "type": "github",
+          "url": "https://github.com/sponsors/jimmywarting"
+        },
+        {
+          "type": "github",
+          "url": "https://paypal.me/jimmywarting"
+        }
+      ],
+      "engines": {
+        "node": ">=10.5.0"
+      }
+    },
     "node_modules/node-fetch": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-3.1.0.tgz",
-      "integrity": "sha512-QU0WbIfMUjd5+MUzQOYhenAazakV7Irh1SGkWCsRzBwvm4fAhzEUaHMJ6QLP7gWT6WO9/oH2zhKMMGMuIrDyKw==",
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-3.1.1.tgz",
+      "integrity": "sha512-SMk+vKgU77PYotRdWzqZGTZeuFKlsJ0hu4KPviQKkfY+N3vn2MIzr0rvpnYpR8MtB3IEuhlEcuOLbGvLRlA+yg==",
       "dependencies": {
         "data-uri-to-buffer": "^4.0.0",
-        "fetch-blob": "^3.1.2",
+        "fetch-blob": "^3.1.3",
         "formdata-polyfill": "^4.0.10"
       },
       "engines": {
@@ -30688,10 +30707,11 @@
       }
     },
     "fetch-blob": {
-      "version": "3.1.2",
-      "resolved": "https://registry.npmjs.org/fetch-blob/-/fetch-blob-3.1.2.tgz",
-      "integrity": "sha512-hunJbvy/6OLjCD0uuhLdp0mMPzP/yd2ssd1t2FCJsaA7wkWhpbp9xfuNVpv7Ll4jFhzp6T4LAupSiV9uOeg0VQ==",
+      "version": "3.1.4",
+      "resolved": "https://registry.npmjs.org/fetch-blob/-/fetch-blob-3.1.4.tgz",
+      "integrity": "sha512-Eq5Xv5+VlSrYWEqKrusxY1C3Hm/hjeAsCGVG3ft7pZahlUAChpGZT/Ms1WmSLnEAisEXszjzu/s+ce6HZB2VHA==",
       "requires": {
+        "node-domexception": "^1.0.0",
         "web-streams-polyfill": "^3.0.3"
       }
     },
@@ -35366,13 +35386,18 @@
         "propagate": "^2.0.0"
       }
     },
+    "node-domexception": {
+      "version": "1.0.0",
+      "resolved": "https://registry.npmjs.org/node-domexception/-/node-domexception-1.0.0.tgz",
+      "integrity": "sha512-/jKZoMpw0F8GRwl4/eLROPA3cfcXtLApP0QzLmUT/HuPCZWyB7IY9ZrMeKw2O/nFIqPQB3PVM9aYm0F312AXDQ=="
+    },
     "node-fetch": {
-      "version": "3.1.0",
-      "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-3.1.0.tgz",
-      "integrity": "sha512-QU0WbIfMUjd5+MUzQOYhenAazakV7Irh1SGkWCsRzBwvm4fAhzEUaHMJ6QLP7gWT6WO9/oH2zhKMMGMuIrDyKw==",
+      "version": "3.1.1",
+      "resolved": "https://registry.npmjs.org/node-fetch/-/node-fetch-3.1.1.tgz",
+      "integrity": "sha512-SMk+vKgU77PYotRdWzqZGTZeuFKlsJ0hu4KPviQKkfY+N3vn2MIzr0rvpnYpR8MtB3IEuhlEcuOLbGvLRlA+yg==",
       "requires": {
         "data-uri-to-buffer": "^4.0.0",
-        "fetch-blob": "^3.1.2",
+        "fetch-blob": "^3.1.3",
         "formdata-polyfill": "^4.0.10"
       },
       "dependencies": {
diff --git a/package.json b/package.json
index 9f1cecf5f0..e6818b9f1b 100644
--- a/package.json
+++ b/package.json
@@ -59,7 +59,7 @@
     "mdast-util-to-string": "^3.1.0",
     "morgan": "^1.10.0",
     "next": "^11.1.3",
-    "node-fetch": "^3.1.0",
+    "node-fetch": "^3.1.1",
     "parse5": "^6.0.1",
     "port-used": "^2.0.8",
     "quick-lru": "6.0.2",
diff --git a/translations/es-ES/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md b/translations/es-ES/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
index 2a958e3494..5f5b793067 100644
--- a/translations/es-ES/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
+++ b/translations/es-ES/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
@@ -18,7 +18,7 @@ shortTitle: Share with your enterprise
 
 ## About {% data variables.product.prodname_actions %} access to internal repositories
 
-If your organization is owned by an enterprise account, you can share actions and workflows within your enterprise, without publishing the action or workflow publicly, by allowing {% data variables.product.prodname_actions %} workflows to access an internal repository that contains the action or workflow.
+Si tu organización le pertenece a una cuenta empresarial, puedes compartir las acciones y flujos de trabajo dentro de tu empresa, sin publicar la acción o flujo de trabajo al público en general, si permites que los flujos de trabajo de {% data variables.product.prodname_actions %} accedan a un repositorio interno que contenga dicha acción o flujo de trabajo.
 
 Any actions or workflows stored in the internal repository can be used in workflows defined in other private and internal repositories owned by the same organization, or by any organization owned by the enterprise. Actions and workflows stored in internal repositories cannot be used in public repositories.
 
diff --git a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 4597daee1f..d6d6c4c2aa 100644
--- a/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/es-ES/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -24,9 +24,9 @@ topics:
 
 Las acciones que utilizas en tu flujo de trabajo pueden definirse en:
 
-- The same repository as your workflow file{% if internal-actions %}
-- An internal repository within the same enterprise account that is configured to allow access to workflows{% endif %}
-- Any public repository
+- El mismo repositorio que tu archivo de flujo de trabajo{% if internal-actions %}
+- Un repositorio interno con la mismo cuenta empresarial que se configuró para permitir el acceso a los flujos de trabajo{% endif %}
+- Cualquier repositorio público
 - Una imagen del contenedor Docker publicada en Docker Hub
 
 {% data variables.product.prodname_marketplace %} es una ubicación central para que encuentres acciones que crea la comunidad de {% data variables.product.prodname_dotcom %}.{% ifversion fpt or ghec %}La [página de {% data variables.product.prodname_marketplace %}](https://github.com/marketplace/actions/) te permite filtrar de acuerdo con la categoría de las acciones. {% endif %}
@@ -45,9 +45,9 @@ Puedes buscar acciones manualmente o por coincidencia exacta directamente en el
 
 ## Agregar una acción a tu flujo de trabajo
 
-You can add an action to your workflow by referencing the action in your workflow file.
+Puedes agregar una acción a tu flujo de trabajo si la referencias en tu archivo de flujo de trabajo.
 
-### Adding an action from {% data variables.product.prodname_marketplace %}
+### Agregar una acción desde {% data variables.product.prodname_marketplace %}
 
 La página de descripción de una acción incluye la versión de la acción y la sintaxis de flujo de trabajo que se necesita para usar la acción. Para mantener estable a tu flujo de trabajo, aún cuando se hagan actualizaciones en una acción, puedes referenciar la versión de la acción a utilizar si especificas el número de etiqueta de Git o de Docker en tu archivo de flujo de trabajo.
 
@@ -60,7 +60,7 @@ La página de descripción de una acción incluye la versión de la acción y la
 
 {% endif %}
 
-### Adding an action from the same repository
+### Agregar una acción desde el mismo repositorio
 
 Si se define una acción en el mismo repositorio en el que tu archivo de flujo de trabajo usa la acción, puedes hacer referencia a la acción con ‌`{owner}/{repo}@{ref}` o la sintaxis `./path/to/dir` en tu archivo de flujo de trabajo.
 
@@ -91,11 +91,11 @@ jobs:
 
 El archivo `action.yml` se utiliza para proporcionar metadatos para la acción. Aprende sobre el contenido de este archivo en la sección "[Sintaxis de metadatos para las GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)."
 
-### Adding an action from a different repository
+### Agregar una acción desde un repositorio diferente
 
-If an action is defined in a different repository than your workflow file, you can reference the action with the `{owner}/{repo}@{ref}` syntax in your workflow file.
+Si se define una acción en un repositorio diferente del de tu archivo de flujo de trabajo, puedes referenciarla con la sintaxis `{owner}/{repo}@{ref}` en tu archivo de flujo de trabajo.
 
-The action must be stored in a public repository{% if internal-actions %} or an internal repository that is configured to allow access to workflows. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}.{% endif %}
+La acción debe almacenarse en un repositorio público{% if internal-actions %} o interno que se configure para permitir el acceso a los flujos de trabajo. Para obtener más información, consulta la sección "[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)".{% else %}.{% endif %}
 
 ```yaml
 jobs:
diff --git a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
index 90f224b925..5898eb6e0a 100644
--- a/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/es-ES/content/actions/using-workflows/reusing-workflows.md
@@ -46,7 +46,7 @@ A reusable workflow can be used by another workflow if {% ifversion ghes or ghec
 
 * Ambos flujos de trabajo están en el mismo repositorio.
 * The called workflow is stored in a public repository.{% ifversion ghes or ghec or ghae %}
-* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. For more information, see {% if internal-actions %}"[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}."{% endif %}
+* El flujo de trabajo llamado se almacena en un repositorio interno y los ajustes de dicho repositorio permiten que se acceda a él. Para obtener más información, consulta la sección {% if internal-actions %}"[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Administrar los ajustes de las {% data variables.product.prodname_actions %} en un repositorio](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}".{% endif %}
 
 ## Using runners
 
diff --git a/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md b/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
index 185c92aef6..8091ac9c66 100644
--- a/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
+++ b/translations/es-ES/content/admin/advanced-security/overview-of-github-advanced-security-deployment.md
@@ -121,32 +121,32 @@ Cuando se inicia una implementación de la GHAS, es importante entender algunos
 
 {% note %}
 
-**Nota:** Si te interesa recibir lecciones subsecuentes sobre tu GHAS, {% data variables.product.prodname_professional_services %} cuenta con diversas opciones de educación y capacitación adicional, incluyendo los temas que tu compañía necesite preparar para GHAS. Estas ofertas podrían mostrarse como talleres, demostraciones y capacitaciones intensivas. Los temas pueden ir desde desplegar la GHAS y mostrar su uso básico hasta algunos más avanzados para seguir desarrollando las habilidades de tu equipo. For more information on working with the {% data variables.product.prodname_professional_services_team %} team, see "[{% data variables.product.prodname_professional_services %}](#github-professional-services)."
+**Nota:** Si te interesa recibir lecciones subsecuentes sobre tu GHAS, {% data variables.product.prodname_professional_services %} cuenta con diversas opciones de educación y capacitación adicional, incluyendo los temas que tu compañía necesite preparar para GHAS. Estas ofertas podrían mostrarse como talleres, demostraciones y capacitaciones intensivas. Los temas pueden ir desde desplegar la GHAS y mostrar su uso básico hasta algunos más avanzados para seguir desarrollando las habilidades de tu equipo. Para obtener más información sobre cómo trabajar con el equipo de {% data variables.product.prodname_professional_services_team %}, consulta la sección "[{% data variables.product.prodname_professional_services %}](#github-professional-services)".
 
 {% endnote %}
 
 
-#### Fact 1: GHAS is a suite of security tools that require action to protect your code.
+#### Hecho 1: La GHAS es una suite de herramientas de seguridad que requiere de una participación activa para proteger tu código.
 
-It’s not security software that is installed and forgotten—just having GHAS on its own does not protect your code. GHAS is a suite of tools that increases with value when configured, maintained, used in daily  workflows, and in combination with other tools.
+No es software de seguridad que se pueda instalar y olvidar; el solo hecho de tener la GHAS no protege tu código. La GHAS es una suite de herramientas que incrementa su valor cuando la configuras, mantienes, utilizas en flujos de trabajo diariamente y la combinas con otras herramientas.
 
-#### Fact 2: GHAS will require adjustment out of the box.
+#### Hecho 2: La GHAS necesitará ajustes tan pronto la implmementes.
 
-Once GHAS is set up on your repositories, there are additional steps that need to be taken to ensure it works for your company’s needs. Code scanning in particular requires further configuration to fine-tune your results, for example, customizing what is flagged by the scans to adjust what is picked up in future scans. Many customers find that initial scans either pick up no results or results that are not relevant based on the application's threat model and need to be adjusted to their company’s needs.
+Una vez que configures la GHAS en tus repositorios, habrán pasos adicionales necesarios para garantizar que funcione de acuerdo con las necesidades de tu compañía. El escaneo de código en particular necesita configurarse aún más para hacer los ajustes más específicos en tus resultados, por ejemplo, personalizar lo que marcan los escaneos para ajustar qué se escogerá en los escaneos futuros. Muchos clientes se encuentran con que los escaneos iniciales ya sea no recogen resultados, o bien, que estos resultados no son relevantes con base en el modelo de amenazas de aplicación y necesitan ajustarse de acuerdo con las necesidades de sus compañías.
 
-#### Fact 3: GHAS tools are most effective when used together, but the most effective AppSec programs involve the use of additional tools/activities.
+#### Hecho 3: Las herramientas de la GHAS tienen su mayor efectividad cuando se utilizan en conjunto, pero los programas más efectivos de AppSec involucran el uso de actividades/herramientas adicionales.
 
-GHAS is most effective when all of the tools are used together. When companies integrate GHAS with other tools and activities, such as penetration testing and dynamic scans, it further improves the effectiveness of the AppSec program. We recommend always utilizing multiple layers of protection.
+La GHAS tiene su mayor efectividad cuando se utilizan todas las herramientas en conjunto. Cuando las compañías integran la GHAS con otras herramientas y actividades, tales como pruebas de penetración y escaneos dinámicos, esta mejora aún más la efectividad del programa de AppSec. Te recomendamos que siempre utilices capas de protección múltiples.
 
-#### Fact 4: Not all companies will use/need custom {% data variables.product.prodname_codeql %} queries, but they can  help you customize/target scan results.
+#### Hecho 4: No todas las compañías utilizarán/necesitarán consultas de {% data variables.product.prodname_codeql %} personalizadas, pero pueden ayudarte a personalizar/apuntar los resultados del escaneo.
 
-Code scanning is powered by {% data variables.product.prodname_codeql %}—the world’s most powerful code analysis engine. While  many companies are excited at the prospect of being able to write custom queries, for a  large portion of our customers the base query set and additional queries available in the  community are typically more than sufficient. However, many companies may find the need  for custom {% data variables.product.prodname_codeql %} queries to help reduce false positives rates in results or crafting new  queries to target results your company may need.
+{% data variables.product.prodname_codeql %}, el motor de análisis de código más poderoso del mundo, impulsa el escaneo de código. Si bien muchas compañías están emocionadas con la posibilidad de poder escribir consultas personalizadas, para la mayoría de ellas, el conjunto básico de consultas y las adicionales disponibles en la comunidad, son habitualmente más que suficiente. Sin embargo, muchas compañías podrían encontrar la necesidad de tener consultas personalizadas de {% data variables.product.prodname_codeql %} para ayudarles a reducir las tasas de falsos positivos en los resultados o para crear consultas nuevas para tratar los resultados que pudiera necesitar tu compañía.
 
-However, if your company is interested in writing custom {% data variables.product.prodname_codeql %} queries, we recommend  you complete your rollout and implementation of GHAS before exploring custom queries.
+Sin embargo, si tu compañía está interesada en escribir consultas personalizadas de {% data variables.product.prodname_codeql %}, te recomendamos completar tu implementación y despliegue de la GHAS antes de explorar esta opción.
 
 {% note %}
 
-**Note:** It’s crucial for your company to have a solid foundation on GHAS before diving deeper into deeper security  practices.
+**Nota:** Es crucial para tu compañía el tener bases sólidas en la GHAS antes de profundizar más en las prácticas de seguridad.
 
 {% endnote %}
 
@@ -196,9 +196,9 @@ Si estás utilizando una versión anterior de GHES (anterior a la 3.0) y te gust
   - "[Mejorar el {% data variables.product.prodname_ghe_server %}](/enterprise-server@2.22/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)"
   - "[Requisitos de mejora](/enterprise-server@2.20/admin/enterprise-management/upgrade-requirements)"
 
-If you’re using a third-party CI/CD system and want to use {% data variables.product.prodname_code_scanning %}, make sure you have downloaded the {% data variables.product.prodname_codeql_cli %}. Para obtener más información, consulta la sección "[Acerca del escaneo de código de CodeQL en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
+Si estás utilizando un sistema de IC/DC y quieres utilizar el {% data variables.product.prodname_code_scanning %}, asegúrate de haber descargado el {% data variables.product.prodname_codeql_cli %}. Para obtener más información, consulta la sección "[Acerca del escaneo de código de CodeQL en tu sistema de IC](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system/about-codeql-code-scanning-in-your-ci-system)."
 
-If you're working with {% data variables.product.prodname_professional_services %} for your GHAS rollout, please be prepared to discuss these items at length in your kickoff meeting.
+Si estás trabajando con los {% data variables.product.prodname_professional_services %} para tu implementación de la GHAS, prepárate para debatir estos elementos a detalle en tu junta de inicio.
 
 {% endif %}
 
@@ -206,60 +206,60 @@ If you're working with {% data variables.product.prodname_professional_services
 
 #### {% data variables.product.prodname_ghe_cloud %}
 
-If you’re a {% data variables.product.prodname_ghe_cloud %} (GHEC) customer there are prerequisites that you’ll need to meet depending on what CI/CD you plan to utilize.
+Si eres un cliente de {% data variables.product.prodname_ghe_cloud %} (GHEC), hay prerrequisitos que necesitarás cumplir dependiendo del plan de IC/DC que utilices.
 
-Using {% data variables.product.prodname_actions %} for your CI/CD:
-- To ensure {% data variables.product.prodname_code_scanning %} can be integrated and utilized properly, you should have a basic understanding of {% data variables.product.prodname_actions %} before proceeding with your installation.
+Utilizar las {% data variables.product.prodname_actions %} para tu IC/DC:
+- Para garantizar que el {% data variables.product.prodname_code_scanning %} puede integrarse y utilizarse de forma adecuada, debes tener un entendimiento básico de las {% data variables.product.prodname_actions %} antes de proceder con tu instalación.
 
-Using a third-party tool for CI/CD:
-- To integrate the {% data variables.product.prodname_codeql_cli %}, you should have a basic understanding of the CI/CD system, as well as *nix and Windows—in particular how commands are executed and how success/failure is signaled. For more information about how to integrate a third-party tool, see "[Using CodeQL code scanning with your existing CI system ](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)."
+Utilizar una herramienta de IC/DC de terceros:
+- Para integrar el {% data variables.product.prodname_codeql_cli %}, debes tener un entendimiento básico del sistema de IC/DC, así como de *nix y Windows; particularmente, la forma en la que se ejecutan los comandos y cómo se señalan los éxitos/fallas. Para obtener más información sobre cómo integrar una herramienta de terceros, consulta la sección "[Utilizar el escaneo de código de CodeQL con tu sistema de IC existente](/code-security/code-scanning/using-codeql-code-scanning-with-your-existing-ci-system)".
 
 {% endif %}
 
-## Partnering with GitHub for your rollout
+## Asociarte con GitHub para tu implementación
 
-As you prepare for your GHAS implementation, it’s important to  consider what will be required from your company to make this  project successful. Our most successful implementations of GHAS  rely on shared responsibilities between both GitHub and our customers throughout the process with a clearly identified stakeholder from the customer owning the project.
+Conforme te preparas para la implementación de la GHAS, es importante considerar lo que se requerirá de tu compañía para que este proyecto tenga éxito. Nuestra implementación más exitosa de la GHAS depende de las responsabilidades compartidas entre GitHub y nuestros clientes a lo largo del proceso, con una identificación clara de los participantes del cliente al que pertenece el proyecto.
 
-#### Success model for customer and GitHub responsibilities
+#### Modelo de éxito para las responsabilidades de GitHub y del cliente
 
-**Customer responsibilities**
-- Completing infrastructure and process prerequisites
-- Managing rollout and implementation, including planning and execution
-- Internal training
-- (Optional) Contributing {% data variables.product.prodname_codeql %} queries to the GitHub Community
+**Responsabilidades del cliente**
+- Completar los prerrequisitos de infraestructura y procesos
+- Administrar la implementación y despliegue, incluyendo la planeación y ejecución
+- Capacitación interna
+- (Opcional) Colaborar con consultas de {% data variables.product.prodname_codeql %} en la comunidad de GitHub
 
-**GitHub responsibilities**
+**Responsabilidades de GitHub**
 
-- Maintenance and enhancements for features, such as {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %}
-- Providing, maintaining, and delivering the following services: {% data variables.product.prodname_dotcom %} Docs, {% data variables.product.prodname_dotcom %} Community, {% data variables.product.prodname_dotcom %} Support
+- Mantenimiento y mejoras para las características, tales como {% ifversion ghes %}{% data variables.product.prodname_ghe_server %}{% endif %}, {% data variables.product.prodname_actions %}, {% data variables.product.prodname_GH_advanced_security %}
+- Proporcionar, mantener y entregar los siguientes servicios: Documentos de {% data variables.product.prodname_dotcom %}, Comunidad de {% data variables.product.prodname_dotcom %}, Soporte de {% data variables.product.prodname_dotcom %}
 
 {% note %}
 
-**Note:**  {% data variables.product.prodname_professional_services %} can help support many of the customer responsibilities. To learn more, see "[GitHub services and support](#github-services-and-support)."
+**Nota:**  Los {% data variables.product.prodname_professional_services %} pueden ayudar a apoyar muchas de las responsabilidades del cliente. Para aprender más, consulta la sección "[Servicios y soporte de GitHub](#github-services-and-support)".
 
 {% endnote %}
 
-## {% data variables.product.prodname_dotcom %} services and support
+## Soporte y servicios de {% data variables.product.prodname_dotcom %}
 
-### {% data variables.product.prodname_dotcom %} Support
+### Soporte de {% data variables.product.prodname_dotcom %}
 
-Si se te presenta algún problema durante tu implementación, puedes buscar las soluciones en nuestra documentación más específica o contactar al Soporte de {% data variables.product.prodname_dotcom %}, el cual es un equipo de ingenieros técnicos especializados que pueden apoyarte cuando tengas problemas. For more information, see "[GitHub Enterprise Support](https://enterprise.github.com/support).
+Si se te presenta algún problema durante tu implementación, puedes buscar las soluciones en nuestra documentación más específica o contactar al Soporte de {% data variables.product.prodname_dotcom %}, el cual es un equipo de ingenieros técnicos especializados que pueden apoyarte cuando tengas problemas. Para obtener más información, consulta la sección "[Soporte de GitHub Enterprise](https://enterprise.github.com/support).
 
-In addition, you can also try our [ {% data variables.product.prodname_gcf %}](https://github.community/).
+Adicionalmente, también puedes probar nuestro [{% data variables.product.prodname_gcf %}](https://github.community/).
 
-If you purchased a Premium Support plan, you can submit your ticket in the [Premium Support Portal](https://enterprise.github.com/support). If you’re unsure of which Support plan you purchased, you can reach out to your sales representative or review the plan options.
+Si compraste un plan de Soporte Premium, puedes emitir tu ticket en el [Portal de Soporte Premium](https://enterprise.github.com/support). Si no estás seguro de qué plan de soporte compraste, puedes contactar a tu representante de ventas o revisar los diferentes planes disponibles.
 
-For more information the Premium support plan options, see:
-  - "[Premium Support](https://github.com/premium-support)" {% ifversion ghec %}
-  - "[About GitHub Premium Support for {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
+Para obtener más información sobre las opciones de plan de soporte Premium, consulta:
+  - "[Soporte Premium](https://github.com/premium-support)" {% ifversion ghec %}
+  - "[Acerca del Soporte Premium de GitHub para {% data variables.product.prodname_ghe_cloud %}](/github/working-with-github-support/about-github-premium-support-for-github-enterprise-cloud)"{% endif %}{% ifversion ghes %}
   - "[Acerca del Soporte Premium de GitHub para {% data variables.product.prodname_ghe_server %}](/admin/enterprise-support/overview/about-github-premium-support-for-github-enterprise-server)"{% endif %}
 
 ### {% data variables.product.prodname_professional_services %}
 
-Our {% data variables.product.prodname_professional_services_team %} team can partner with you for a successful rollout and implementation of {% data variables.product.prodname_GH_advanced_security %}. Ofrecemos varias opciones para el tipo de orientación y apoyo que esperas necesitar para tu implementación. También tenemos capacitación habitual e intensiva disponible para ayudar a que tu compañía optimice el valor de la GHAS.
+Nuestro equipo de {% data variables.product.prodname_professional_services_team %} puede asociarse contigo para que tengas una implementación y despliegue exitosos de la {% data variables.product.prodname_GH_advanced_security %}. Ofrecemos varias opciones para el tipo de orientación y apoyo que esperas necesitar para tu implementación. También tenemos capacitación habitual e intensiva disponible para ayudar a que tu compañía optimice el valor de la GHAS.
 
 Si te gustaría trabajar con nuestro equipo de {% data variables.product.prodname_professional_services_team %} para tu implementación, te recomendamos que comiences a pensar en tu diseño e infraestructura de sistema, así como en la cantidad de repositorios que quieres configurar con GHAS, para comenzar con estas conversiones. Adicionalmente, comienza a pensar en las metas que te gustaría lograr con esta implementación.
 
-Implementation is just one step in a successful security-driven journey where you’ll learn how to use GHAS. Once you’ve completed your implementation, there will be more to learn with the rollout throughout your infrastructure and codebases. Speak with your sales representative for more information about all the {% data variables.product.prodname_professional_services_team %} options available.
+La implementación es tan solo un paso en este camino de éxito impulsado por la seguridad, en donde aprenderás a utilizar la GHAS. Una vez que hayas completado tu implementación, habrá más que aprender con la implementación a lo largo de tu infraestructura y bases de código. Habla con tu representante de ventas para obtener más información sobre todas las opciones de {% data variables.product.prodname_professional_services_team %} disponibles.
 
-If you initially opted out of additional services, but find that additional support is  needed as you begin your implementation, please reach out to your sales representative to discuss what services options may be needed to support your implementation.
+Si inicialmente decidiste no adoptar nuestros servicios adicionales, pero te diste cuenta de que necesitas apoyo adicional para comenzar tu implementación, contacta a tu representante de ventas para debatir las opciones de servicio que pudieras requerir para apoyar tu implementación.
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md
index 7cc695ec88..e43dbe0ab0 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/about-github-connect.md
@@ -12,13 +12,13 @@ topics:
 
 ## Acerca de {% data variables.product.prodname_github_connect %}
 
-{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}.
+{% data variables.product.prodname_github_connect %} amplía a {% data variables.product.product_name %} permitiendo a {% data variables.product.product_location %} beneficiarse del poder de {% data variables.product.prodname_dotcom_the_website %} de forma limitada. Después de que habilites {% data variables.product.prodname_github_connect %}, podrás habilitar características y flujos de trabajo adicionales que dependen de {% data variables.product.prodname_dotcom_the_website %}, tales como {% ifversion ghes or ghae-issue-4864 %}las {% data variables.product.prodname_dependabot_alerts %} para las vulnerabilidades de seguridad que se rastrean en la {% data variables.product.prodname_advisory_database %}{% else %}permitiendo a los usuarios utilizar acciones impulsadas por la comunidad de {% data variables.product.prodname_dotcom_the_website %} en sus archivos de flujo de trabajo{% endif %}.
 
 {% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
 
 Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
 
-To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.product.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+Para habilitar {% data variables.product.prodname_github_connect %}, configuras una conexión entre {% data variables.product.product_location %} y la cuenta de organización o empresa de {% data variables.product.prodname_dotcom_the_website %} que utilice {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
 
 After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
 
@@ -26,17 +26,17 @@ After enabling {% data variables.product.prodname_github_connect %}, you will be
 
 After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise.
 
-| Característica                                                     | Descripción                                                                                                                                                                                                                                     | Más información                                                                                                                                                                                                                                                                                       |
-| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %}
+| Característica                                                     | Descripción                                                                                                                                                                                                                                     | Más información                                                                                                                                                                                                                                                                                                        |
+| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %}
 | Automatic user license sync                                        | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %}
-| {% data variables.product.prodname_dependabot_alerts %}          | Allow users to find and fix vulnerabilities in code dependencies.                                                                                                                                                                               | "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %}  for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)"{% endif %}
-| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files.                                                                                                                                   | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)" |
-| Unified search                                                     | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}.                                                  | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"                                                                                                                  |
-| Unified contributions                                              | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.                             | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"                                                                                                    |
+| {% data variables.product.prodname_dependabot_alerts %}          | Allow users to find and fix vulnerabilities in code dependencies.                                                                                                                                                                               | "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %}  para tu empresa](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)"{% endif %}
+| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files.                                                                                                                                   | "[Habilitar el acceso automático a las acciones de {% data variables.product.prodname_dotcom_the_website %} utilizando {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)" |
+| Unified search                                                     | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}.                                                  | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"                                                                                                                                   |
+| Unified contributions                                              | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.                             | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"                                                                                                                     |
 
 ## Data transmission for {% data variables.product.prodname_github_connect %}
 
-When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection.
+Cuando habilitas {% data variables.product.prodname_github_connect %} o características específicas de {% data variables.product.prodname_github_connect %}, un registro en las tiendas de {% data variables.product.prodname_ghe_cloud %} almacena la siguiente información sobre la conexión.
 {% ifversion ghes %}
 - La parte pública de la clave de tu licencia {% data variables.product.prodname_ghe_server %}
 - Un hash de tu licencia {% data variables.product.prodname_ghe_server %}
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
index e64ea66b59..f0cdae4493 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
@@ -22,7 +22,7 @@ shortTitle: Automatic user license sync
 
 After you enable license synchronization, you'll be able to view license usage for your entire enterprise across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} sincroniza la licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %} semanalmente. Paa obtener más información, consulta la sección "[Administrar tu licencia de {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)".
 
-También puedes cargar en forma manual información de licencias de usuario {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+También puedes cargar en forma manual información de licencias de usuario {% data variables.product.prodname_ghe_server %} en {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Sincronizar el uso de licencia entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)".
 
 ## Habilitar la sincronización de licencias
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md
index 1a8c2adc9a..a4ada428d9 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md
@@ -55,7 +55,7 @@ Si habilitas la detección de vulnerabilidades, cuando {% data variables.product
 ### Prerrequisitos
 
 Para que {% data variables.product.product_location %} detecte las dependencias vulnerables y genere {% data variables.product.prodname_dependabot_alerts %}:
-- You must enable {% data variables.product.prodname_github_connect %}. {% ifversion ghae %}This also enables the dependency graph service.{% endif %}{% ifversion ghes or ghae %}For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."{% endif %}
+- You must enable {% data variables.product.prodname_github_connect %}. {% ifversion ghae %}Esto también habilita el servicio de la gráfica de dependencias.{% endif %}{% ifversion ghes or ghae %}Para obtener más información, consulta la sección "[Administrar {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)".{% endif %}
 {% ifversion ghes %}- Debes habilitar el servicio de gráficas de dependencia.{% endif %}
 - Debes habilitar el escaneo de vulnerabilidades.
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
index 5d4f3c58b2..8e22f2b3ac 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
@@ -27,7 +27,7 @@ topics:
 
 Como propietario de empresa, puedes permitir que los usuarios finales envíen cuentas de contribuciones anonimizadas para su trabajo desde {% data variables.product.product_location %} hacia su gráfica de contribuciones de {% data variables.product.prodname_dotcom_the_website %}.
 
-After you enable {% data variables.product.prodname_unified_contributions %}, before individual users can send contribution counts from {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, each user must also connect their personal account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)".
+Después de habilitar las {% data variables.product.prodname_unified_contributions %}, antes de que los usuarios individuales puedan enviar conteos de contribuciones de {% data variables.product.product_location %} a {% data variables.product.prodname_dotcom_the_website %}, cada uno de ellos también debe conectar su cuenta personal de {% data variables.product.product_name %} con una cuenta personal de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Enviar contribuciones empresariales a tu perfil de {% data variables.product.prodname_dotcom_the_website %}](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)".
 
 {% data reusables.github-connect.sync-frequency %}
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
index 242dc2df61..5e19e700a4 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
@@ -26,13 +26,13 @@ topics:
 
 {% data reusables.github-connect.beta %}
 
-When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}.
+Cuando habilitas la búsqueda unificada, los usuarios pueden ver los resultados de búsqueda desde el contenido de {% data variables.product.prodname_dotcom_the_website %} cuando buscan desde {% data variables.product.product_location %}{% ifversion ghae %} en {% data variables.product.prodname_ghe_managed %}{% endif %}.
 
 You can choose to allow search results for public repositories on {% data variables.product.prodname_dotcom_the_website %}, and you can separately choose to allow search results for private repositories on {% data variables.product.prodname_ghe_cloud %}. If you enable unified search for private repositories, users can only search private repositories that they have access to and that are owned by the connected organization or enterprise account. Para obtener más información, consulta [Acerca de buscar en {% data variables.product.prodname_dotcom %}](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)".
 
 Users will never be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments.
 
-After you enable unified search for {% data variables.product.product_location %}, before individual users can see search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location %}, each user must also connect their personal account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} en tu cuenta de empresa privada](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)".
+Después de habilitar la búsqueda unificada para {% data variables.product.product_location %}, antes de que los usuarios individuales puedan ver los resultados de búsqueda de {% data variables.product.prodname_dotcom_the_website %} en {% data variables.product.product_location %}, cada uno de ellos también debe conectar su cuenta personal de {% data variables.product.product_name %} con una cuenta personal de {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información, consulta la sección "[Habilitar la búsqueda de repositorios de {% data variables.product.prodname_dotcom_the_website %} en tu cuenta de empresa privada](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)".
 
 Buscar a través de las API REST y GraphQL no incluye {% data variables.product.prodname_dotcom_the_website %} los resultados de búsqueda. No están admitidas la búsqueda avanzada y buscar wikis en {% data variables.product.prodname_dotcom_the_website %}.
 
diff --git a/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md
index ba94b6bcbb..2846ae909c 100644
--- a/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md
+++ b/translations/es-ES/content/admin/configuration/configuring-github-connect/managing-github-connect.md
@@ -48,9 +48,9 @@ To configure a connection, your proxy configuration must allow connectivity to `
 
 Los propietarios de empresa que también son propietarios de una cuenta de empresa u organización que utiliza {% data variables.product.prodname_ghe_cloud %} pueden habilitar {% data variables.product.prodname_github_connect %}.
 
-If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner.
+Si estás conectando a {% data variables.product.product_location %} a una organización en {% data variables.product.prodname_ghe_cloud %} que no le pertenezca a una cuenta empresarial, debes iniciar sesión en {% data variables.product.prodname_dotcom_the_website %} como propietario de organización.
 
-If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner.
+Si estás conectando {% data variables.product.product_location %} a una organización de {% data variables.product.prodname_ghe_cloud %} que le pertenezca a una cuenta empresarial o si la conectas a la cuenta empresarial misma, deberás iniciar sesión en {% data variables.product.prodname_dotcom_the_website %} como propietario de empresa.
 
 {% ifversion ghes %}
 1. Iniciar sesión en {% data variables.product.product_location %} y {% data variables.product.prodname_dotcom_the_website %}.
diff --git a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 3ff90e3a64..89fbf119a4 100644
--- a/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/es-ES/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -75,50 +75,50 @@ Para obtener más información sobre cómo crear o acceder a tu ID de llave de a
    * Tu ID de llave de acceso. Por ejemplo, `ABCAIOSFODNN7EXAMPLE1`.
    * Tu llave secreta. Por ejemplo, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
 
-   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
+   ![Ingresar la configuración de transmisión](/assets/images/help/enterprises/audit-stream-add-s3.png)
 
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Amazon S3 endpoint.
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} pueda conectarse y escribir en la terminal de Amazon S3.
 
    ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check.png)
 
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
-### Setting up streaming to Azure Blob Storage
+### Configurar la transmisión hacia Azure Blob Storage
 
-Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)."
+Antes de configurar una transmisión en {% data variables.product.prodname_dotcom %}, primero debes haber creado una cuenta de almacenamiento y un contenedor en Microsoft Azure. Para obtener más detalles, consulta la sección de "[Introducción a Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)" em la documentación de Microsoft.
 
-To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
+Para configurar la transmisión en {% data variables.product.prodname_dotcom %}, necesitarás la URL de un token SAS.
 
 **En el portal de Microsoft Azure**:
-1. On the Home page, click **Storage Accounts**.
-2. Click the name of the storage account you want to use, then click **Containers**.
+1. En la página principal, haz clic en **Cuentas de almacenamiento**.
+2. Haz clic en el nombre de la cuenta de almacenamiento que quieras utilizar y luego en **Contenedores**.
 
-   ![The Containers link in Azure](/assets/images/azure/azure-storage-containers.png)
+   ![El enlace de contenedores en Azure](/assets/images/azure/azure-storage-containers.png)
 
-1. Click the name of the container you want to use.
-1. Click **Shared access tokens**.
+1. Haz clic en el nombre del contenedor que quieres utilizar.
+1. Haz clic en **Tokens de acceso compartidos**.
 
-   ![The shared access token link in Azure](/assets/images/azure/azure-storage-shared-access-tokens.png)
+   ![El enlace de token de acceso compartido en Azure](/assets/images/azure/azure-storage-shared-access-tokens.png)
 
-1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
+1. En el menú desplegable de **Permisos**, cambia los permisos para solo permitir `Create` y `Write`.
 
-   ![The permissions drop-down menu](/assets/images/azure/azure-storage-permissions.png)
+   ![El menú desplegable de permisos](/assets/images/azure/azure-storage-permissions.png)
 
-1. Set an expiry date that complies with your secret rotation policy.
-1. Click **Generate SAS token and URL**.
-1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
+1. Configura una fecha de vencimiento que cumpla con tu política de rotación de secretos.
+1. Haz clic en **Generar un token SAS y URL**.
+1. Copia el valor del campo **Blob SAS URL** que se muestra. Utilizarás esta URL en {% data variables.product.prodname_dotcom %}.
 
 **En {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Blob Storage**.
+1. Haz clic en **Configurar transmisión** y selecciona **Azure Blob Storage**.
 
-   ![Choose Azure Blob Storage from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azureblob.png)
+   ![Elige Azure Blob Storage en el menú desplegable](/assets/images/help/enterprises/audit-stream-choice-azureblob.png)
 
-1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
+1. En la página de configuración, ingresa la URL de SAS del blob que copiaste en Azure. El campo **Contenedor** se llena automáticamente con base en la URL.
 
-   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azureblob.png)
+   ![Ingresar la configuración de transmisión](/assets/images/help/enterprises/audit-stream-add-azureblob.png)
 
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} pueda conectarse a la terminal de Azure Blob Storage.
 
    ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check.png)
 
@@ -131,11 +131,11 @@ Antes de configurar una transmisión en {% data variables.product.prodname_dotco
 Necesitas dos partes de información sobre tu concentrador de eventos: su nombre de instancia y la secuencia de conexión.
 
 **En el portal de Microsoft Azure**:
-1. Search for "Event Hubs".
+1. Busca "Event Hubs".
 
-   ![The Azure portal search box](/assets/images/azure/azure-resources-search.png)
+   ![La caja de búsqueda del portal de Azure](/assets/images/azure/azure-resources-search.png)
 
-1. Select **Event Hubs**. Se listarán los nombres de tus concentradores de eventos.
+1. Selecciona **Event Hubs**. Se listarán los nombres de tus concentradores de eventos.
 
    ![Una lista de concentradores de eventos](/assets/images/help/enterprises/azure-event-hubs-list.png)
 
@@ -159,9 +159,9 @@ Necesitas dos partes de información sobre tu concentrador de eventos: su nombre
    * El nombre de la instancia de Azure Event Hubs.
    * La secuencia de conexión.
 
-   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
+   ![Ingresar la configuración de transmisión](/assets/images/help/enterprises/audit-stream-add-azure.png)
 
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en la terminal de Azure Events Hub.
 
    ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check.png)
 
@@ -214,12 +214,12 @@ Para transmitir bitácoras de auditoría a la terminal del Recolector de Eventos
 
    * Un token que pueda utilizar {% data variables.product.prodname_dotcom %} para autenticarse a la aplicación de terceros.
 
-   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+   ![Ingresar la configuración de transmisión](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
 1. Deja seleccionada la casilla de **Habilitar la verificación por SSL**.
 
     Las bitácoras de auditoría siempre se transmiten como datos cifrados, sin embargo, si seleccionas esta opción, {% data variables.product.prodname_dotcom %} verificará el certificado SSL de tu instancia de Splunk cuando entregue eventos. La verificación por SSL te ayuda a garantizar que los eventos se entreguen a tu terminal URL con seguridad. Puedes limpiar la selección de esta opción, pero te recomendamos que dejes habilitada la verificación por SSL.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Haz clic en **Verificar terminal** para verificar que {% data variables.product.prodname_dotcom %} puede conectarse y escribir en la terminal de Splunk. ![Verificar la terminal](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ## Pausar la transmisión de bitácoras de auditoría
diff --git a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
index 0140eef130..03690f920a 100644
--- a/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/es-ES/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -22,7 +22,7 @@ Para obtener más información sobre las licencias y el uso de {% data variables
 
 ## Sincronizar el uso de licencias automáticamente
 
-Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de la licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
+Puedes utilizar {% data variables.product.prodname_github_connect %} para sincronizar de forma automática el conteo y el uso de la licencia de usuario entre {% data variables.product.prodname_ghe_server %} y {% data variables.product.prodname_ghe_cloud %}. Para obtener más información, consulta la sección "[Habilitar la sincronización automática de licencias de usuario para tu empresa]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" en la documentación de {% data variables.product.prodname_ghe_server %}{% elsif ghes %}".{% endif %}
 
 ## Sincronizar el uso de licencias manualmente
 
diff --git a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index beb4c1367f..c85d937834 100644
--- a/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/es-ES/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
@@ -33,7 +33,7 @@ Cuando el {% data variables.product.prodname_dependabot %} detecta las dependenc
 {% ifversion ghes or ghae-issue-4864 %}
 Predeterminadamente, si el propietario de tu empresa configuró las notificaciones por correo electrónico en ella, recibirás las {% data variables.product.prodname_dependabot_alerts %} por este medio.
 
-Los propietarios de empresas también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
+Los propietarios de empresas también pueden habilitar las {% data variables.product.prodname_dependabot_alerts %} sin notificaciones. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)".
 {% endif %}
 
 ## Configurar las notificaciones para las {% data variables.product.prodname_dependabot_alerts %}
diff --git a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 7d547f5f81..d13b66f0c8 100644
--- a/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/es-ES/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -43,6 +43,9 @@ Archivos compatibles:
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
+{%- if svg-support %}
+* SVG (*.svg*)
+{%- endif %}
 * Archivos de registro (*.log*)
 * Documentos de Microsoft Word (*.docx*), Powerpoint (*.pptx*) y Excel (*.xlsx*)
 * Archivos de texto (*.txt*)
diff --git a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index 040b2bae7d..a1638c32d0 100644
--- a/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/es-ES/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -120,7 +120,7 @@ También pueden configurarse los permisos predeterminados en los ajustes de la o
 
 Los miembros de tu empresa pueden utilizar repositorios internos para trabajar en proyectos sin compartir información públicamente. Para obtener más información, consulta la sección "[Acerca de los repositorios](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)".
 
-You can configure whether {% if internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% if internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% endif %}
+Puedes configurar si se puede acceder a{% if internal-actions%}las acciones y {% endif %}flujos de trabajo de un repositorio interno desde fuera de este.{% if internal-actions %} Para obtener más información, consulta la sección "[Compartir acciones y flujos de trabajo con tu empresa](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)".{% endif %}
 
 1. En {% data variables.product.prodname_dotcom %}, navega hasta la página principal del repositorio interno.
 1. Debajo de tu nombre de repositorio, haz clic en {% octicon "gear" aria-label="The gear icon" %}**Configuración**.
@@ -129,9 +129,9 @@ You can configure whether {% if internal-actions%}actions and {% endif %}workflo
 
    {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png){% else %}![Set the access to Actions components](/assets/images/enterprise/3.4/actions-access-settings.png){% endif %}
 
-   * **Not accessible** - Workflows in other repositories cannot access this repository.
-   * **Accessible from repositories in the 'ORGANIZATION NAME' organization** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ORGANIZATION NAME' organization can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.{% endif %}
-   * **Accessible from repositories in the 'ENTERPRISE NAME' enterprise** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ENTERPRISE NAME' enterprise can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.{% endif %}
+   * **Sin acceso** - Los flujos de trabajo en otros repositorios no pueden acceder a este.
+   * **Con acceso desde los repositorios de la organización 'ORGANIZATION NAME'** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Los flujos de trabajo en otros repositorios que sean parte de la organización 'ORGANIZATION NAME' pueden acceder a las acciones y flujos de trabajo de este repositorio. Se permite el acceso solo desde los repositorios internos o privados.{% else %}Los flujos de trabajo en otros repositorios pueden utilizar flujos de trabajo en este si son parte de la misma organización y su visibilidad es privada o interna.{% endif %}
+   * **Con acceso desde los repositorios de la empresa 'ENTERPRISE NAME'** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Los flujos de trabajo en otros repositorios que son parte de la empresa 'ENTERPRISE NAME' pueden acceder a las acciones y flujos de trabajo de este repositorio. Se permite el acceso únicamente desde los repositorios internos o privados.{% else %}Los flujos de trabajo en otros repositorios pueden utilizar aquellos en este repositorio si son parte de la misma empresa y su visibilidad es privada o interna.{% endif %}
 1. Da clic en **Guardar** para aplicar la configuración.
 {% endif %}
 
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index e7e91091ed..f733fb3910 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -70,8 +70,8 @@ Si tuilizas {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_se
 
 {% ifversion fpt or ghes or ghec %}
 
-- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
-- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_managed %} documentation
+- "[Habilitar la {% data variables.product.prodname_unified_search %} en tu empresa]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" en la documentación de {% data variables.product.prodname_ghe_server %}{% endif %}
+- "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" en la documentación de {% data variables.product.prodname_ghe_managed %}
 
 {% ifversion ghes or ghae %}
 
diff --git a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index ed02780199..d707c596be 100644
--- a/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/es-ES/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -25,8 +25,8 @@ Puedes buscar repositorios privados designados en {% data variables.product.prod
 ## Prerrequisitos
 
 - Un propietario de empresa de {% ifversion fpt or ghec %}tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %}{% data variables.product.product_name %}{% endif %} debe habilitar {% data variables.product.prodname_github_connect %} y {% data variables.product.prodname_unified_search %}. Para obtener más información, consulta lo siguiente.{% ifversion fpt or ghes or ghec %}
-  - "\[Enabling {% data variables.product.prodname_unified_search %} for your enterprise\](/{% ifversion not ghes %}enterprise-server@latest/{% endif %}admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
-  - "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise}](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
+  - "\[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa\](/{% ifversion not ghes %}enterprise-server@latest/{% endif %}admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise"{% ifversion fpt or ghec %} en la documentación de {% data variables.product.prodname_ghe_server %}{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
+  - "[Habilitar la {% data variables.product.prodname_unified_search %} para tu empresa}](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"{% ifversion fpt or ghec %} en la documentación de {% data variables.product.prodname_ghe_managed %}{% endif %}
 {% endif %}
 
 - Ya debes tener acceso a los repositorios privados y conectar tu cuenta {% ifversion fpt or ghec %}en tu ambiente privado de {% data variables.product.prodname_enterprise %}{% else %} en {% data variables.product.product_name %}{% endif %} con tu cuenta en {% data variables.product.prodname_dotcom_the_website %}. Para obtener más información sobre los repositorios en los que puedes buscar, consulta la sección "[Acerca de cómo buscar en GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)".
diff --git a/translations/es-ES/data/features/svg-support.yml b/translations/es-ES/data/features/svg-support.yml
new file mode 100644
index 0000000000..6636cc97e6
--- /dev/null
+++ b/translations/es-ES/data/features/svg-support.yml
@@ -0,0 +1,6 @@
+---
+#Releases issue #1951
+#Support upload of SVG files
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml b/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml
index d583122605..27229aa0a8 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-0/23.yml
@@ -1,7 +1,7 @@
 date: '2022-01-18'
 sections:
   security_fixes:
-    - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
+    - 'Se actualizaron los paquetes a las versiones de seguridad más recientes. En estas actualizaciones, Log4j se actualizó a la versión 2.17.1. Nota: Las mitigaciones que se lanzaron previamente en las versiones 3.3.1, 3.2.6, 3.1.14 y 3.0.22 son suficientes para tratar el impacto de las CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones de GitHub Enterprise Server.'
     - 'Sanitize more secrets in the generated support bundles'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml b/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml
index 47f3ed158c..ac97a66a81 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-1/15.yml
@@ -1,7 +1,7 @@
 date: '2022-01-18'
 sections:
   security_fixes:
-    - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
+    - 'Se actualizaron los paquetes a las versiones de seguridad más recientes. En estas actualizaciones, Log4j se actualizó a la versión 2.17.1. Nota: Las mitigaciones que se lanzaron previamente en las versiones 3.3.1, 3.2.6, 3.1.14 y 3.0.22 son suficientes para tratar el impacto de las CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones de GitHub Enterprise Server.'
     - 'Sanitize more secrets in the generated support bundles'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml b/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml
index 2b25e58fa2..6c42b19b54 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-2/7.yml
@@ -1,7 +1,7 @@
 date: '2022-01-18'
 sections:
   security_fixes:
-    - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
+    - 'Se actualizaron los paquetes a las versiones de seguridad más recientes. En estas actualizaciones, Log4j se actualizó a la versión 2.17.1. Nota: Las mitigaciones que se lanzaron previamente en las versiones 3.3.1, 3.2.6, 3.1.14 y 3.0.22 son suficientes para tratar el impacto de las CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones de GitHub Enterprise Server.'
     - 'Sanitize more secrets in the generated support bundles'
     - 'Los paquetes se actualizaron a las últimas versiones de seguridad.'
   bugs:
diff --git a/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml b/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
index 06c8e858ab..9881a6d2c2 100644
--- a/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
+++ b/translations/es-ES/data/release-notes/enterprise-server/3-3/2.yml
@@ -1,7 +1,7 @@
 date: '2022-01-18'
 sections:
   security_fixes:
-    - 'Packages have been updated to the latest security versions. In these updates, Log4j has been updated to version 2.17.1. Note: previous mitigations released in 3.3.1, 3.2.6, 3.1.14, and 3.0.22 are sufficient to address the impact of CVE-2021-44228, CVE-2021-45046, CVE-2021-45105, and CVE-2021-44832 in these versions of GitHub Enterprise Server.'
+    - 'Se actualizaron los paquetes a las versiones de seguridad más recientes. En estas actualizaciones, Log4j se actualizó a la versión 2.17.1. Nota: Las mitigaciones que se lanzaron previamente en las versiones 3.3.1, 3.2.6, 3.1.14 y 3.0.22 son suficientes para tratar el impacto de las CVE-2021-44228, CVE-2021-45046, CVE-2021-45105 y CVE-2021-44832 en estas versiones de GitHub Enterprise Server.'
     - 'Sanitize more secrets in the generated support bundles'
     - 'Users on teams with the Security Manger role will now be notified about security alerts for repositories they are watching.'
     - 'The security managers component will show a less-aggressive warning once the maximum number of teams has been reached.'
diff --git a/translations/es-ES/data/reusables/actions/internal-actions-summary.md b/translations/es-ES/data/reusables/actions/internal-actions-summary.md
index 3efefb4211..df2927347c 100644
--- a/translations/es-ES/data/reusables/actions/internal-actions-summary.md
+++ b/translations/es-ES/data/reusables/actions/internal-actions-summary.md
@@ -1,3 +1,3 @@
 {% if internal-actions %}
-To share actions across your enterprise without publishing the actions publicly, you can store the actions in an internal repository, then configure the repository to allow access to {% data variables.product.prodname_actions %} workflows in other repositories owned by the same organization or by any organization in the enterprise. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
+Para compartir las acciones en toda tu empresa sin publicarlas públicamente, puedes almacenarlas en un repositorio interno y luego configurarlo para que acceda a los flujos de trabajo de las {% data variables.product.prodname_actions %} en otros repositorios que le pertenezcan a la misma organización o a cualquier organización de la empresa. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
 {% endif %}
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
index f07cb5b55b..b45486739c 100644
--- a/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
+++ b/translations/es-ES/data/reusables/actions/jobs/setting-default-values-for-jobs-defaults-run.md
@@ -1,8 +1,8 @@
-You can use `defaults.run` to provide default `shell` and `working-directory` options for all [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) steps in a workflow. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs.<job_id>.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave.
+Puedes utilizar `defaults.run` para proporcionar opciones predeterminadas de `shell` y `working-directory` para todos los pasos de [`run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun) en un flujo de trabajo. También puedes configurar ajustes predeterminados para `run` que solo estén disponibles para un job. Para obtener más información, consulta [`jobs.<job_id>.defaults.run`](/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_iddefaultsrun). No podrás utilizar contextos o expresiones en esta palabra clave.
 
 {% data reusables.github-actions.defaults-override %}
 
-#### Example: Set the default shell and working directory
+#### Ejemplo: Configurar el directorio de trabajo y shell predeterminados
 
 ```yaml
 defaults:
diff --git a/translations/es-ES/data/reusables/actions/outside-collaborators-internal-actions.md b/translations/es-ES/data/reusables/actions/outside-collaborators-internal-actions.md
index fcf164b2d1..93f612f183 100644
--- a/translations/es-ES/data/reusables/actions/outside-collaborators-internal-actions.md
+++ b/translations/es-ES/data/reusables/actions/outside-collaborators-internal-actions.md
@@ -1 +1 @@
-If you make an internal repository in your enterprise accessible to {% data variables.product.prodname_actions %} workflows in other repositories, outside collaborators on the other repositories can indirectly access the internal repository, even though they do not have direct access to the internal repository. The outside collaborators can view logs for workflow runs when actions or workflows from the internal repository are used.
\ No newline at end of file
+Si haces que los flujos de trabajo de las {% data variables.product.prodname_actions %} de otros repositorios puedan acceder a un repositorio interno de tu empresa, los colaboradores externos de otros repositorios podrán acceder a él indirectamente a pesar de que no tengan acceso directo a él. The outside collaborators can view logs for workflow runs when actions or workflows from the internal repository are used.
\ No newline at end of file
diff --git a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
index 14d6ad3175..f44494e0fe 100644
--- a/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
+++ b/translations/es-ES/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
@@ -1,3 +1,3 @@
 {% ifversion ghes or ghae-issue-4864 %}
-El mismo propietario de la empresa configura la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} a nivel empresarial. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
+El mismo propietario de la empresa configura la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} a nivel empresarial. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)".
 {% endif %} 
diff --git a/translations/es-ES/data/reusables/repositories/enable-security-alerts.md b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md
index cbeb54eb7f..68b645fe6b 100644
--- a/translations/es-ES/data/reusables/repositories/enable-security-alerts.md
+++ b/translations/es-ES/data/reusables/repositories/enable-security-alerts.md
@@ -1,4 +1,4 @@
 {% ifversion ghes or ghae-issue-4864 %}
 Los propietarios de empresas deben habilitar
-las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables de {% data variables.product.product_location %} antes de que puedas utilizar esta característica. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
+las {% data variables.product.prodname_dependabot_alerts %} para las dependencias vulnerables de {% data variables.product.product_location %} antes de que puedas utilizar esta característica. Para obtener más información, consulta la sección "[Habilitar la gráfica de dependencias y las {% data variables.product.prodname_dependabot_alerts %} en tu cuenta empresarial](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)".
 {% endif %}
diff --git a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
index 702c4358f8..027eeacccb 100644
--- a/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
+++ b/translations/ja-JP/content/account-and-profile/setting-up-and-managing-your-github-user-account/managing-user-account-settings/managing-your-tab-size-rendering-preference.md
@@ -3,7 +3,7 @@ title: Managing your tab size rendering preference
 intro: You can manage the number of spaces a tab is equal to for your user account.
 versions:
   fpt: '*'
-  ghae: ghae-issue-5083
+  ghae: issue-5083
   ghes: '>=3.4'
   ghec: '*'
 topics:
diff --git a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
index 00fecf9091..a1a81cc4f1 100644
--- a/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
+++ b/translations/ja-JP/content/actions/creating-actions/about-custom-actions.md
@@ -26,7 +26,7 @@ topics:
 You can create actions by writing custom code that interacts with your repository in any way you'd like, including integrating with {% data variables.product.prodname_dotcom %}'s APIs and any publicly available third-party API. For example, an action can publish npm modules, send SMS alerts when urgent issues are created, or deploy production-ready code.
 
 {% ifversion fpt or ghec %}
-You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built, your repository must be public.
+You can write your own actions to use in your workflow or share the actions you build with the {% data variables.product.prodname_dotcom %} community. To share actions you've built with everyone, your repository must be public. {% if internal-actions %}To share actions only within your enterprise, your repository must be internal.{% endif %}
 {% endif %}
 
 Actions can run directly on a machine or in a Docker container. You can define an action's inputs, outputs, and environment variables.
@@ -69,7 +69,10 @@ If you're developing an action for other people to use, we recommend keeping the
 Storing an action in its own repository makes it easier for the {% data variables.product.prodname_dotcom %} community to discover the action, narrows the scope of the code base for developers fixing issues and extending the action, and decouples the action's versioning from the versioning of other application code.
 {% endif %}
 
-{% ifversion fpt or ghec %}If you're building an action that you don't plan to make available to the public, you {% else %} You{% endif %} can store the action's files in any location in your repository. If you plan to combine action, workflow, and application code in a single repository, we recommend storing actions in the `.github` directory. For example, `.github/actions/action-a` and `.github/actions/action-b`.
+{% data reusables.actions.internal-actions-summary %}
+
+{% ifversion fpt or ghec %}If you're building an action that you don't plan to make available to others, you {% else %} You{% endif %} can store the action's files in any location in your repository. If you plan to combine action, workflow, and application code in a single repository, we recommend storing actions in the `.github` directory. For example, `.github/actions/action-a` and `.github/actions/action-b`.
+
 
 ## Compatibility with {% data variables.product.prodname_ghe_server %}
 
diff --git a/translations/ja-JP/content/actions/creating-actions/index.md b/translations/ja-JP/content/actions/creating-actions/index.md
index d88d7d4703..1e17641fc4 100644
--- a/translations/ja-JP/content/actions/creating-actions/index.md
+++ b/translations/ja-JP/content/actions/creating-actions/index.md
@@ -21,6 +21,7 @@ children:
   - /dockerfile-support-for-github-actions
   - /setting-exit-codes-for-actions
   - /publishing-actions-in-github-marketplace
+  - /sharing-actions-and-workflows-with-your-enterprise
   - /releasing-and-maintaining-actions
   - /developing-a-third-party-cli-action
 ---
diff --git a/translations/ja-JP/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md b/translations/ja-JP/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
new file mode 100644
index 0000000000..2ef62be64e
--- /dev/null
+++ b/translations/ja-JP/content/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise.md
@@ -0,0 +1,39 @@
+---
+title: Sharing actions and workflows with your enterprise
+intro: You can share an action or workflow with your enterprise without publishing the action or workflow publicly.
+versions:
+  feature: internal-actions
+type: tutorial
+topics:
+  - Actions
+  - Action development
+shortTitle: Share with your enterprise
+---
+
+{% note %}
+
+**Note:** Allowing workflows to access actions in internal repositories is currently in beta and subject to change.
+
+{% endnote %}
+
+## About {% data variables.product.prodname_actions %} access to internal repositories
+
+If your organization is owned by an enterprise account, you can share actions and workflows within your enterprise, without publishing the action or workflow publicly, by allowing {% data variables.product.prodname_actions %} workflows to access an internal repository that contains the action or workflow.
+
+Any actions or workflows stored in the internal repository can be used in workflows defined in other private and internal repositories owned by the same organization, or by any organization owned by the enterprise. Actions and workflows stored in internal repositories cannot be used in public repositories.
+
+{% warning %}
+
+**Warning**: {% data reusables.actions.outside-collaborators-internal-actions %}
+
+{% endwarning %}
+
+## Sharing actions and workflows with your enterprise
+
+1. Store the action or workflow in an internal repository. For more information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
+1. Configure the repository to allow access to workflows in other private and internal repositories. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)."
+
+## 参考リンク
+
+- 「[Enterprise アカウントについて](/admin/overview/about-enterprise-accounts)」
+- "[Reusing workflows](/actions/using-workflows/reusing-workflows)"
diff --git a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
index 5b71215cd5..ef41c90bec 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/finding-and-customizing-actions.md
@@ -24,8 +24,9 @@ topics:
 
 The actions you use in your workflow can be defined in:
 
-- A public repository
-- The same repository where your workflow file references the action
+- The same repository as your workflow file{% if internal-actions %}
+- An internal repository within the same enterprise account that is configured to allow access to workflows{% endif %}
+- Any public repository
 - A published Docker container image on Docker Hub
 
 {% data variables.product.prodname_marketplace %} is a central location for you to find actions created by the {% data variables.product.prodname_dotcom %} community.{% ifversion fpt or ghec %} [{% data variables.product.prodname_marketplace %} page](https://github.com/marketplace/actions/) enables you to filter for actions by category. {% endif %}
@@ -46,6 +47,10 @@ You can search and browse actions directly in your repository's workflow editor.
 
 ## Adding an action to your workflow
 
+You can add an action to your workflow by referencing the action in your workflow file. 
+
+### Adding an action from {% data variables.product.prodname_marketplace %}
+
 An action's listing page includes the action's version and the workflow syntax required to use the action. To keep your workflow stable even when updates are made to an action, you can reference the version of the action to use by specifying the Git or Docker tag number in your workflow file.
 
 1. Navigate to the action you want to use in your workflow.
@@ -58,6 +63,66 @@ An action's listing page includes the action's version and the workflow syntax r
 
 {% endif %}
 
+### Adding an action from the same repository
+
+If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
+
+Example repository file structure:
+
+```
+|-- hello-world (repository)
+|   |__ .github
+|       └── workflows
+|           └── my-first-workflow.yml
+|       └── actions
+|           |__ hello-world-action
+|               └── action.yml
+```
+
+Example workflow file:
+
+```yaml
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      # This step checks out a copy of your repository.
+      - uses: actions/checkout@v2
+      # This step references the directory that contains the action.
+      - uses: ./.github/actions/hello-world-action
+```
+
+The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)."
+
+### Adding an action from a different repository
+
+If an action is defined in a different repository than your workflow file, you can reference the action with the `{owner}/{repo}@{ref}` syntax in your workflow file.
+
+The action must be stored in a public repository{% if internal-actions %} or an internal repository that is configured to allow access to workflows. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% else %}.{% endif %}
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: actions/setup-node@v1.1.0
+```
+
+### Referencing a container on Docker Hub
+
+If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
+
+```yaml
+jobs:
+  my_first_job:
+    steps:
+      - name: My first step
+        uses: docker://alpine:3.8
+```
+
+For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
+
+
 ## Using release management for your custom actions
 
 The creators of a community action have the option to use tags, branches, or SHA values to manage releases of the action. Similar to any dependency, you should indicate the version of the action you'd like to use based on your comfort with automatically accepting updates to the action.
@@ -127,51 +192,6 @@ outputs:
 By default, you can use most of the official {% data variables.product.prodname_dotcom %}-authored actions in {% data variables.product.prodname_ghe_managed %}. For more information, see "[Using actions in {% data variables.product.prodname_ghe_managed %}](/admin/github-actions/using-actions-in-github-ae)."
 {% endif %}
 
-## Referencing an action in the same repository where a workflow file uses the action
-
-If an action is defined in the same repository where your workflow file uses the action, you can reference the action with either the ‌`{owner}/{repo}@{ref}` or `./path/to/dir` syntax in your workflow file.
-
-Example repository file structure:
-
-```
-|-- hello-world (repository)
-|   |__ .github
-|       └── workflows
-|           └── my-first-workflow.yml
-|       └── actions
-|           |__ hello-world-action
-|               └── action.yml
-```
-
-Example workflow file:
-
-```yaml
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      # This step checks out a copy of your repository.
-      - uses: actions/checkout@v2
-      # This step references the directory that contains the action.
-      - uses: ./.github/actions/hello-world-action
-```
-
-The `action.yml` file is used to provide metadata for the action. Learn about the content of this file in "[Metadata syntax for GitHub Actions](/actions/creating-actions/metadata-syntax-for-github-actions)"
-
-## Referencing a container on Docker Hub
-
-If an action is defined in a published Docker container image on Docker Hub, you must reference the action with the `docker://{image}:{tag}` syntax in your workflow file. To protect your code and data, we strongly recommend you verify the integrity of the Docker container image from Docker Hub before using it in your workflow.
-
-```yaml
-jobs:
-  my_first_job:
-    steps:
-      - name: My first step
-        uses: docker://alpine:3.8
-```
-
-For some examples of Docker actions, see the [Docker-image.yml workflow](https://github.com/actions/starter-workflows/blob/main/ci/docker-image.yml) and "[Creating a Docker container action](/articles/creating-a-docker-container-action)."
-
 ## Next steps
 
 To continue learning about {% data variables.product.prodname_actions %}, see "[Essential features of {% data variables.product.prodname_actions %}](/actions/learn-github-actions/essential-features-of-github-actions)."
diff --git a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
index 93b313661f..786494ff08 100644
--- a/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
+++ b/translations/ja-JP/content/actions/learn-github-actions/understanding-github-actions.md
@@ -64,6 +64,8 @@ An _action_ is a custom application for the {% data variables.product.prodname_a
 
 You can write your own actions, or you can find actions to use in your workflows in the {% data variables.product.prodname_marketplace %}.
 
+{% data reusables.actions.internal-actions-summary %}
+
 詳細については、「[アクションを作成する](/actions/creating-actions)」を参照してください。
 
 ### ランナー
diff --git a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
index e649582ef8..31a6985618 100644
--- a/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
+++ b/translations/ja-JP/content/actions/security-guides/security-hardening-for-github-actions.md
@@ -196,6 +196,12 @@ To help mitigate the risk of an exposed token, consider restricting the assigned
 The same principles described above for using third-party actions also apply to using third-party workflows. You can help mitigate the risks associated with reusing workflows by following the same good practices outlined above. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
 
+{% if internal-actions %}
+## Allowing workflows to access internal repositories
+
+{% data reusables.actions.outside-collaborators-internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
+{% endif %}
+
 ## Potential impact of a compromised runner
 
 These sections consider some of the steps an attacker can take if they're able to run malicious commands on a {% data variables.product.prodname_actions %} runner.
@@ -232,14 +238,14 @@ The attacker server can use the {% ifversion fpt or ghec %}{% data variables.pro
 
 ## リポジトリ間のアクセスを検討する
 
-{% data variables.product.prodname_actions %} は、意図的に一度に単一のリポジトリに対してスコープされます。 The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。
+{% data variables.product.prodname_actions %} is intentionally scoped for a single repository at a time. The `GITHUB_TOKEN` grants the same level of access as a write-access user, because any write-access user can access this token by creating or modifying a workflow file{% ifversion fpt or ghes > 3.1 or ghae or ghec %}, elevating the permissions of the `GITHUB_TOKEN` if necessary{% endif %}. ユーザはリポジトリごとに特定の権限を持っているため、1 つのリポジトリの `GITHUB_TOKEN` に別のリポジトリへのアクセスを許可すると、慎重に実装しない場合 {% data variables.product.prodname_dotcom %} 権限モデルに影響します。 同様に、{% data variables.product.prodname_dotcom %} 認証トークンをワークフローに追加する場合は注意が必要です。これは、コラボレータに誤って広範なアクセスを付与することにより、{% data variables.product.prodname_dotcom %} アクセス許可モデルにも影響を与える可能性があるためです。
 
 [{% data variables.product.prodname_dotcom %} ロードマップ](https://github.com/github/roadmap/issues/74)では、{% data variables.product.product_name %} 内のリポジトリ間アクセスを可能にするフローをサポートする計画がありますが、この機能はまだサポートされていません。 現在、権限のあるリポジトリ間のやり取りを実行する唯一の方法は、ワークフロー内に {% data variables.product.prodname_dotcom %} 認証トークンまたは SSH キーをシークレットとして配置することです。 多くの認証トークンタイプでは特定のリソースへの詳細なアクセスが許可されていないことから、意図したものよりはるかに広範なアクセスを許可できるため、間違ったトークンタイプを使用すると重大なリスクが生じます。
 
 次のリストでは、ワークフロー内のリポジトリデータにアクセスするための推奨アプローチを優先度の高い順に説明しています。
 
 1. **`GITHUB_TOKEN`**
-    -  This token is intentionally scoped to the single repository that invoked the workflow, and {% ifversion fpt or ghes > 3.1 or ghae or ghec %}can have {% else %}has {% endif %}the same level of access as a write-access user on the repository. トークンは各ジョブが開始する前に作成され、ジョブが終了すると期限切れになります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
+    -  このトークンは、ワークフローを呼び出した単一のリポジトリに意図的にスコープされており、リポジトリの書き込みアクセスを持つユーザと同じレベルのアクセス権を{% ifversion fpt or ghes > 3.1 or ghae or ghec %}持つ{% else %}ことができます{% endif %}。 トークンは各ジョブが開始する前に作成され、ジョブが終了すると期限切れになります。 詳しい情報については「[GITHUB_TOKENでの認証](/actions/configuring-and-managing-workflows/authenticating-with-the-github_token)」を参照してください。
     - 可能な場合は、常に `GITHUB_TOKEN` を使用する必要があります。
 2. **リポジトリのデプロイキー**
     - デプロイキーは、単一のリポジトリへの読み取りまたは書き込みアクセスを許可する唯一の認証情報タイプの 1 つであり、ワークフロー内の別のリポジトリとのやり取りに使用できます。 詳しい情報については、「[デプロイキーを管理する](/developers/overview/managing-deploy-keys#deploy-keys)」を参照してください。
@@ -295,7 +301,7 @@ Organizationの管理タスクをモニタするために、監査ログを使
 
 たとえば、監査ログを使用して、Organization のシークレットへの変更を追跡する `org.update_actions_secret` イベントを追跡できます。 ![監査ログのエントリ](/assets/images/help/repository/audit-log-entries.png)
 
-以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 監査ログの使用に関する詳しい情報については、「[Organization の監査ログのレビュー](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)」を参照してください。
+以下の表は、監査ログにある{% data variables.product.prodname_actions %}のイベントを示します。 For more information on using the audit log, see "[Reviewing the audit log for your organization](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#searching-the-audit-log)."
 
 {% ifversion fpt or ghec %}
 ### 環境のイベント
@@ -330,7 +336,7 @@ Organizationの管理タスクをモニタするために、監査ログを使
 | ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `enterprise.register_self_hosted_runner`  | 新しいセルフホストランナーが登録されたときにトリガーされます。 詳しい情報については「[Enterpriseへのセルフホストランナーの追加](/actions/hosting-your-own-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-an-enterprise)」を参照してください。                                                                                                                                                                                                                        |
 | `enterprise.remove_self_hosted_runner`    | セルフホストランナーが削除されたときにトリガーされます。                                                                                                                                                                                                                                                                                                                                                                                        |
-| `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list is updated. For more information, see "[Set self-hosted runners in a group for an organization](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)."{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
+| `enterprise.runner_group_runners_updated` | Triggered when a runner group's member list is updated. 詳しい情報については、「[Organizationのグループにセルフホストランナーを設定する](/rest/reference/actions#set-self-hosted-runners-in-a-group-for-an-organization)」を参照してください。{% ifversion fpt or ghes > 3.1  or ghae or ghec %}
 | `enterprise.self_hosted_runner_online`    | Triggered when the runner application is started. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."                                                                     |
 | `enterprise.self_hosted_runner_offline`   | Triggered when the runner application is stopped. Can only be viewed using the REST API; not visible in the UI or JSON/CSV export. For more information, see "[Checking the status of a self-hosted runner](/actions/hosting-your-own-runners/monitoring-and-troubleshooting-self-hosted-runners#checking-the-status-of-a-self-hosted-runner)."{% endif %}
 | `enterprise.self_hosted_runner_updated`   | ランナーアプリケーションが更新されたときにトリガーされます。 REST API と UI を使用して表示できます。 Audit log を JSON データまたは CSV ファイルとしてエクスポートする場合、このイベントは含まれません。 詳しい情報については、「[セルフホストランナーについて](/actions/hosting-your-own-runners/about-self-hosted-runners#about-self-hosted-runners)」および「[Organization の Audit log をレビューする](/organizations/keeping-your-organization-secure/reviewing-the-audit-log-for-your-organization#exporting-the-audit-log)」を参照してください。 |
diff --git a/translations/ja-JP/content/actions/using-workflows/advanced-workflow-features.md b/translations/ja-JP/content/actions/using-workflows/advanced-workflow-features.md
index d4c95e2259..df1cf877c1 100644
--- a/translations/ja-JP/content/actions/using-workflows/advanced-workflow-features.md
+++ b/translations/ja-JP/content/actions/using-workflows/advanced-workflow-features.md
@@ -164,7 +164,10 @@ To learn more about self-hosted runner labels, see ["Using labels with self-host
 To learn more about {% data variables.product.prodname_dotcom %}-hosted runner labels, see ["Supported runners and hardware resources"](/actions/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources).
 {% endif %}
 
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+## Reusing workflows
 {% data reusables.actions.reusable-workflows %}
+{% endif %}
 
 {% ifversion fpt or ghes > 3.0 or ghae or ghec %}
 
diff --git a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
index f4730e0cef..ec01a5048e 100644
--- a/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
+++ b/translations/ja-JP/content/actions/using-workflows/reusing-workflows.md
@@ -46,7 +46,7 @@ A reusable workflow can be used by another workflow if {% ifversion ghes or ghec
 
 * Both workflows are in the same repository.
 * The called workflow is stored in a public repository.{% ifversion ghes or ghec or ghae %}
-* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see "[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository)."{% endif %}
+* The called workflow is stored in an internal repository and the settings for that repository allow it to be accessed. For more information, see {% if internal-actions %}"[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise){% else %}"[Managing {% data variables.product.prodname_actions %} settings for a repository](/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#allowing-access-to-components-in-an-internal-repository){% endif %}."{% endif %}
 
 ## Using runners
 
diff --git a/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md b/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
index c795c20b48..9987878f91 100644
--- a/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
+++ b/translations/ja-JP/content/actions/using-workflows/sharing-workflows-secrets-and-runners-with-your-organization.md
@@ -20,11 +20,29 @@ type: how_to
 
 ワークフローやその他の {% data variables.product.prodname_actions %} 機能を Team と共有する必要がある場合は、{% data variables.product.prodname_dotcom %} Organization 内でのコラボレーションを検討します。 Organization を使用すると、シークレット、成果物、およびセルフホストランナーを一元的に保存および管理できます。 You can also create starter workflows in the `.github` repository and share them with other users in your organization.
 
-## Using starter workflows
+## Sharing {% if internal-actions %}actions and {% endif %}workflows
 
-{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
+{% if internal-actions %}
+You can share both individual actions and entire workflows with your organization, with or without publishing the actions or workflows publicly. You can reuse actions and workflows exactly by referencing them in your workflow file, and you can create starter workflows that provide templates for new workflows.
+{% else %}
+Your organization can share workflows by reusing the workflows exactly or by creating starter workflows that provide templates for new workflows.
+{% endif %}
+
+{% if internal-actions %}
+### Sharing actions with your enterprise
+
+{% data reusables.actions.internal-actions-summary %}
+{% endif %}
+
+{% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
+### Reusing workflows
 
 {% data reusables.actions.reusable-workflows %}
+{% endif %}
+
+### Using starter workflows
+
+{% data reusables.actions.workflow-organization-templates %} For more information, see "[Creating starter workflows for your organization](/actions/using-workflows/creating-starter-workflows-for-your-organization)."
 
 ## Organization 内でシークレットを共有する
 
diff --git a/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
index 36f5a8456f..a3672c7bae 100644
--- a/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
+++ b/translations/ja-JP/content/admin/advanced-security/enabling-github-advanced-security-for-your-enterprise.md
@@ -54,7 +54,7 @@ For guidance on a phased deployment of GitHub Advanced Security, see "[Deploying
 
     - {% data variables.product.prodname_code_scanning_capc %}, see "[Configuring {% data variables.product.prodname_code_scanning %} for your appliance](/admin/advanced-security/configuring-code-scanning-for-your-appliance#prerequisites-for-code-scanning)."
     - {% data variables.product.prodname_secret_scanning_caps %}, see "[Configuring {% data variables.product.prodname_secret_scanning %} for your appliance](/admin/advanced-security/configuring-secret-scanning-for-your-appliance#prerequisites-for-secret-scanning)."{% endif %}
-    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+    - {% data variables.product.prodname_dependabot %}, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 
 ## Enabling and disabling {% data variables.product.prodname_GH_advanced_security %} features
 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md
new file mode 100644
index 0000000000..7aa1c0e97c
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/about-github-connect.md
@@ -0,0 +1,72 @@
+---
+title: About GitHub Connect
+intro: '{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by giving you access to additional features and workflows that rely on the power of {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: overview
+topics:
+  - Enterprise
+  - GitHub Connect
+---
+
+## {% data variables.product.prodname_github_connect %} について
+
+{% data variables.product.prodname_github_connect %} enhances {% data variables.product.product_name %} by allowing {% data variables.product.product_location %} to benefit from the power of {% data variables.product.prodname_dotcom_the_website %} in limited ways. After you enable {% data variables.product.prodname_github_connect %}, you can enable additional features and workflows that rely on {% data variables.product.prodname_dotcom_the_website %}, such as {% ifversion ghes or ghae-issue-4864 %}{% data variables.product.prodname_dependabot_alerts %} for security vulnerabilities that are tracked in the {% data variables.product.prodname_advisory_database %}{% else %}allowing users to use community-powered actions from {% data variables.product.prodname_dotcom_the_website %} in their workflow files{% endif %}.
+
+{% data variables.product.prodname_github_connect %} does not open {% data variables.product.product_location %} to the public internet. None of your enterprise's private data is exposed to {% data variables.product.prodname_dotcom_the_website %} users. Instead, {% data variables.product.prodname_github_connect %} transmits only the limited data needed for the individual features you choose to enable. Unless you enable license sync, no personal data is transmitted by {% data variables.product.prodname_github_connect %}. For more information about what data is transmitted by {% data variables.product.prodname_github_connect %}, see "[Data transmission for {% data variables.product.prodname_github_connect %}](#data-transmission-for-github-connect)."
+
+Enabling {% data variables.product.prodname_github_connect %} will not allow {% data variables.product.prodname_dotcom_the_website %} users to make changes to {% data variables.product.product_name %}.
+
+To enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.product.product_location %} and an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+After enabling {% data variables.product.prodname_github_connect %}, you will be able to enable features such as {% ifversion ghes %}automatic user license sync and {% endif %}{% data variables.product.prodname_dependabot_alerts %}. For more information about all of the features available, see "[{% data variables.product.prodname_github_connect %} features](#github-connect-features)."
+
+## {% data variables.product.prodname_github_connect %} features
+
+After you configure the connection between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %}, you can enable individual features of {% data variables.product.prodname_github_connect %} for your enterprise.
+
+| 機能                                                                 | 説明                                                                                                                                                                                                                                              | 詳細情報                                                                                                                                                                                                                                                                                                  |
+| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |{% ifversion ghes %}
+| Automatic user license sync                                        | Manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}. | "[Enabling automatic user license sync for your enterprise](/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise)"{% endif %}{% ifversion ghes or ghae-issue-4864 %}
+| {% data variables.product.prodname_dependabot_alerts %}          | Allow users to find and fix vulnerabilities in code dependencies.                                                                                                                                                                               | "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %}  for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)"{% endif %}
+| {% data variables.product.prodname_dotcom_the_website %} actions | Allow users to use actions from {% data variables.product.prodname_dotcom_the_website %} in workflow files.                                                                                                                                   | "[Enabling automatic access to {% data variables.product.prodname_dotcom_the_website %} actions using {% data variables.product.prodname_github_connect %}](/admin/github-actions/managing-access-to-actions-from-githubcom/enabling-automatic-access-to-githubcom-actions-using-github-connect)" |
+| Unified search                                                     | Allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}.                                                  | "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"                                                                                                                  |
+| Unified contributions                                              | Allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.                             | "[Enabling {% data variables.product.prodname_unified_contributions %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise)"                                                                                                    |
+
+## Data transmission for {% data variables.product.prodname_github_connect %}
+
+When you enable {% data variables.product.prodname_github_connect %} or specific {% data variables.product.prodname_github_connect %} features, a record on {% data variables.product.prodname_ghe_cloud %} stores the following information about the connection.
+{% ifversion ghes %}
+- {% data variables.product.prodname_ghe_server %} ライセンスの公開鍵の部分
+- {% data variables.product.prodname_ghe_server %} ライセンスのハッシュ
+- {% data variables.product.prodname_ghe_server %} ライセンスの顧客名
+- The version of {% data variables.product.product_location_enterprise %}{% endif %}
+- The hostname of {% data variables.product.product_location %}
+- The organization or enterprise account on {% data variables.product.prodname_ghe_cloud %} that's connected to {% data variables.product.product_location %}
+- The authentication token that's used by {% data variables.product.product_location %} to make requests to {% data variables.product.prodname_ghe_cloud %}
+- If Transport Layer Security (TLS) is enabled and configured on {% data variables.product.product_location %}{% ifversion ghes %}
+- The {% data variables.product.prodname_github_connect %} features that are enabled on {% data variables.product.product_location %}, and the date and time of enablement{% endif %}
+
+{% data variables.product.prodname_github_connect %} syncs the above connection data between {% data variables.product.product_location %} and {% data variables.product.prodname_ghe_cloud %} weekly, from the day and approximate time that {% data variables.product.prodname_github_connect %} was enabled.
+
+{% note %}
+
+**Note:** No repositories, issues, or pull requests are ever transmitted by {% data variables.product.prodname_github_connect %}.
+
+{% endnote %}
+
+Additional data is transmitted if you enable individual features of {% data variables.product.prodname_github_connect %}.
+
+| 機能                                                                 | Data                                                                                      | Which way does the data flow?                                                                                                                                                                                                                    | Where is the data used?                                                                               |
+| ------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |{% ifversion ghes %}
+| Automatic user license sync                                        | Each {% data variables.product.product_name %} user's user ID and email addresses         | From {% data variables.product.product_name %} to {% data variables.product.prodname_ghe_cloud %}                                                                                                                                              | {% data variables.product.prodname_ghe_cloud %} |{% endif %}{% ifversion ghes or ghae-issue-4864 %}
+| {% data variables.product.prodname_dependabot_alerts %}          | Vulnerability alerts                                                                      | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}                                                                                                                                   | {% data variables.product.product_name%} 
+{% endif %}
+| {% data variables.product.prodname_dotcom_the_website %} actions | Name of action, action (YAML file from {% data variables.product.prodname_marketplace %}) | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}
+| Unified search                                                     | Search terms, search results                                                              | From {% data variables.product.prodname_dotcom_the_website %} to {% data variables.product.product_name %}<br><br>From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %} | {% data variables.product.product_name %}
+| Unified contributions                                              | Contribution counts                                                                       | From {% data variables.product.product_name %} to {% data variables.product.prodname_dotcom_the_website %}                                                                                                                                   | {% data variables.product.prodname_dotcom_the_website %}
+
+## 参考リンク
+
+- "[Enterprise accounts](/graphql/guides/managing-enterprise-accounts)" in the GraphQL API documentation
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
new file mode 100644
index 0000000000..307cd30cfe
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise.md
@@ -0,0 +1,32 @@
+---
+title: Enabling automatic user license sync for your enterprise
+intro: 'You can manage license usage across your {% data variables.product.prodname_enterprise %} deployments by automatically syncing user licenses from {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}.'
+redirect_from:
+  - /enterprise/admin/installation/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /enterprise/admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+permissions: 'Site administrators for {% data variables.product.prodname_ghe_server %} who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable automatic user license synchronization.'
+versions:
+  ghes: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - Licensing
+shortTitle: Automatic user license sync
+---
+
+## ライセンスの同期について
+
+After you enable license synchronization, you'll be able to view license usage for your entire enterprise across {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.prodname_github_connect %} は、{% data variables.product.prodname_ghe_server %} と {% data variables.product.prodname_ghe_cloud %} 間で毎週ライセンスを同期します。 For more information, see "[Managing your license for {% data variables.product.prodname_enterprise %}](/billing/managing-your-license-for-github-enterprise)."
+
+{% data variables.product.prodname_ghe_server %}ユーザライセンス情報を手動で{% data variables.product.prodname_ghe_cloud %}にアップロードすることもできます。 For more information, see "[Syncing license usage between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}](/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud)."
+
+## ライセンス同期の有効化
+
+Before enabling license synchronization on {% data variables.product.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}
+1. [Server can sync user license count and usage] で、ドロップダウンメニューを使って [**Enabled**] を選択します。 ![自動ユーザライセンス同期を有効化するドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-user-license-drop-down.png)
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md
new file mode 100644
index 0000000000..f2c6c8b0f1
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise.md
@@ -0,0 +1,127 @@
+---
+title: Enabling the dependency graph and Dependabot alerts for your enterprise
+intro: 'You can allow users on {% data variables.product.product_location %} to find and fix vulnerabilities in code dependencies by enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %}.'
+miniTocMaxHeadingLevel: 3
+shortTitle: Dependabot
+redirect_from:
+  - /enterprise/admin/installation/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /enterprise/admin/configuration/enabling-security-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /enterprise/admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-alerts-for-vulnerable-dependencies-on-github-enterprise-server
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account
+permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.product_location %}.'
+versions:
+  ghes: '*'
+  ghae: issue-4864
+type: how_to
+topics:
+  - Enterprise
+  - Security
+  - Dependency graph
+  - Dependabot
+---
+
+## {% data variables.product.product_location %} 上の脆弱性のある依存関係に対するアラートについて
+
+{% data reusables.dependabot.dependabot-alerts-beta %}
+
+{% data variables.product.prodname_dotcom %} identifies vulnerable dependencies in repositories and creates {% data variables.product.prodname_dependabot_alerts %} on {% data variables.product.product_location %}, using:
+
+- Data from the {% data variables.product.prodname_advisory_database %}
+- The dependency graph service
+
+For more information about these features, see "[About the dependency graph](/github/visualizing-repository-data-with-graphs/about-the-dependency-graph)" and "[About alerts for vulnerable dependencies](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies)."
+
+### About synchronization of data from the {% data variables.product.prodname_advisory_database %}
+
+{% data reusables.repositories.tracks-vulnerabilities %}
+
+You can connect {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %} with {% data variables.product.prodname_github_connect %}. Once connected, vulnerability data is synced from the {% data variables.product.prodname_advisory_database %} to your instance once every hour. また、脆弱性データはいつでも手動で同期することができます。 {% data variables.product.product_location %} からのコードまたはコードに関する情報は、{% data variables.product.prodname_dotcom_the_website %} にアップロードされません。
+
+Only {% data variables.product.company_short %}-reviewed advisories are synchronized. {% data reusables.security-advisory.link-browsing-advisory-db %}
+
+### About scanning of repositories with synchronized data from the {% data variables.product.prodname_advisory_database %}
+
+For repositories with {% data variables.product.prodname_dependabot_alerts %} enabled, scanning is triggered on any push to the default branch that contains a manifest file or lock file. Additionally, when a new vulnerability record is added to the instance, {% data variables.product.prodname_ghe_server %} scans all existing repositories in that instance and generates alerts for any repository that is vulnerable. For more information, see "[Detection of vulnerable dependencies](/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/about-alerts-for-vulnerable-dependencies#detection-of-vulnerable-dependencies)."
+
+### About generation of {% data variables.product.prodname_dependabot_alerts %}
+
+If you enable vulnerability detection, when {% data variables.product.product_location %} receives information about a vulnerability, it identifies repositories in your instance that use the affected version of the dependency and generates {% data variables.product.prodname_dependabot_alerts %}. You can choose whether or not to notify users automatically about new {% data variables.product.prodname_dependabot_alerts %}.
+
+## Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies on {% data variables.product.product_location %}
+
+### 必要な環境
+
+For {% data variables.product.product_location %} to detect vulnerable dependencies and generate {% data variables.product.prodname_dependabot_alerts %}:
+- You must enable {% data variables.product.prodname_github_connect %}. {% ifversion ghae %}This also enables the dependency graph service.{% endif %}{% ifversion ghes or ghae %}For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."{% endif %}
+{% ifversion ghes %}- You must enable the dependency graph service.{% endif %}
+- You must enable vulnerability scanning.
+
+{% ifversion ghes %}
+{% ifversion ghes > 3.1 %}
+You can enable the dependency graph via the {% data variables.enterprise.management_console %} or the administrative shell. We recommend you follow the {% data variables.enterprise.management_console %} route unless {% data variables.product.product_location %} uses clustering.
+
+### Enabling the dependency graph via the {% data variables.enterprise.management_console %}
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.management-console %}
+{% data reusables.enterprise_management_console.advanced-security-tab %}
+1. Under "Security," click **Dependency graph**. ![Checkbox to enable or disable the dependency graph](/assets/images/enterprise/3.2/management-console/enable-dependency-graph-checkbox.png)
+{% data reusables.enterprise_management_console.save-settings %}
+1. **Visit your instance（インスタンスへのアクセス）**をクリックしてください。
+
+### Enabling the dependency graph via the administrative shell
+{% endif %}{% ifversion ghes < 3.2 %}
+### 依存関係グラフの有効化
+{% endif %}
+{% data reusables.enterprise_site_admin_settings.sign-in %}
+1. In the administrative shell, enable the dependency graph on {% data variables.product.product_location %}:
+    {% ifversion ghes > 3.1 %}```shell
+    ghe-config app.dependency-graph.enabled true
+    ```
+    {% else %}```shell
+    ghe-config app.github.dependency-graph-enabled true
+  ghe-config app.github.vulnerability-alerting-and-settings-enabled true
+    ```{% endif %}
+   {% note %}
+
+   **Note**: For more information about enabling access to the administrative shell via SSH, see "[Accessing the administrative shell (SSH)](/enterprise/{{ currentVersion }}/admin/configuration/accessing-the-administrative-shell-ssh)."
+
+   {% endnote %}
+2. 設定を適用します。
+    ```shell
+    $ ghe-config-apply
+    ```
+3. {% data variables.product.prodname_ghe_server %}に戻ります。
+{% endif %}
+
+### {% data variables.product.prodname_dependabot_alerts %} の有効化
+
+{% ifversion ghes %}
+Before enabling {% data variables.product.prodname_dependabot_alerts %} for your instance, you need to enable the dependency graph. For more information, see above.
+{% endif %}
+
+{% data reusables.enterprise-accounts.access-enterprise %}
+{%- ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}
+{% data reusables.enterprise-accounts.github-connect-tab %}
+1. Under "Repositories can be scanned for vulnerabilities", select the drop-down menu and click **Enabled without notifications**. Optionally, to enable alerts with notifications, click **Enabled with notifications**. ![脆弱性に対するリポジトリのスキャンを有効化するドロップダウンメニュー](/assets/images/enterprise/site-admin-settings/enable-vulnerability-scanning-in-repositories.png)
+
+   {% tip %}
+
+   **Tip**: We recommend configuring {% data variables.product.prodname_dependabot_alerts %} without notifications for the first few days to avoid an overload of emails. 数日後、通知を有効化すれば、通常どおり {% data variables.product.prodname_dependabot_alerts %} を受信できます。
+
+   {% endtip %}
+
+{% ifversion fpt or ghec or ghes > 3.2 %}
+When you enable {% data variables.product.prodname_dependabot_alerts %}, you should consider also setting up {% data variables.product.prodname_actions %} for {% data variables.product.prodname_dependabot_security_updates %}. This feature allows developers to fix vulnerabilities in their dependencies. For more information, see "[Setting up {% data variables.product.prodname_dependabot %} security and version updates on your enterprise](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates)."
+{% endif %}
+
+## {% data variables.product.product_location %}で脆弱性のある依存関係を表示する
+
+{% data variables.product.product_location %}ですべての脆弱性を表示し、{% data variables.product.prodname_dotcom_the_website %}から脆弱性データを手動で同期して、リストを更新することができます。
+
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+2. 左サイドバーで [**Vulnerabilities**] をクリックします。 ![サイト管理サイドバーの [Vulnerabilities] タブ](/assets/images/enterprise/business-accounts/vulnerabilities-tab.png)
+3. 脆弱性データを同期するには、[**Sync Vulnerabilities now**] をクリックします。 ![[Sync vulnerabilities now] ボタン](/assets/images/enterprise/site-admin-settings/sync-vulnerabilities-button.png)
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
new file mode 100644
index 0000000000..4a0b5af9bb
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise.md
@@ -0,0 +1,53 @@
+---
+title: Enabling unified contributions for your enterprise
+shortTitle: Unified contributions
+intro: 'You can allow users to include anonymized contribution counts for their work on {% data variables.product.product_location %} in their contribution graphs on {% data variables.product.prodname_dotcom_the_website %}.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-contributions-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom
+permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified contributions between {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+---
+
+{% data reusables.github-connect.beta %}
+
+## About unified contributions
+
+As an enterprise owner, you can allow end users to send anonymized contribution counts for their work from {% data variables.product.product_location %} to their {% data variables.product.prodname_dotcom_the_website %} contribution graph.
+
+After you enable {% data variables.product.prodname_unified_contributions %}, before individual users can send contribution counts from {% data variables.product.product_location %} to {% data variables.product.prodname_dotcom_the_website %}, each user must also connect their personal account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Sending enterprise contributions to your {% data variables.product.prodname_dotcom_the_website %} profile](/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-graphs-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile)."
+
+{% data reusables.github-connect.sync-frequency %}
+
+If the enterprise owner disables the functionality or individual users opt out of the connection, the contribution counts from {% data variables.product.product_name %} will be deleted on {% data variables.product.prodname_dotcom_the_website %}. If the user reconnects their profiles after disabling them, the contribution counts for the past 90 days are restored.
+
+{% data variables.product.product_name %} は、接続されているユーザーのコントリビューションカウントおよびソース ({% data variables.product.product_name %}) **のみ**を送信します。 コントリビューションまたはその作成方法に関する情報は送信されません。
+
+## Enabling unified contributions
+
+Before enabling {% data variables.product.prodname_unified_contributions %} on {% data variables.product.product_location %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% ifversion ghes %}
+{% data reusables.github-connect.access-dotcom-and-enterprise %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.business %}
+{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. Under "Users can share contribution counts to {% data variables.product.prodname_dotcom_the_website %}", click **Request access**. ![Request access to unified contributions option](/assets/images/enterprise/site-admin-settings/dotcom-ghe-connection-request-access.png){% ifversion ghes %}
+2. {% data variables.product.prodname_ghe_server %} サイトに[サインイン](https://enterprise.github.com/login)して、以降の指示を受けてください。
+
+When you request access, we may redirect you to the {% data variables.product.prodname_ghe_server %} site to check your current terms of service.
+{% endif %}
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
new file mode 100644
index 0000000000..f0841098cf
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise.md
@@ -0,0 +1,51 @@
+---
+title: Enabling unified search for your enterprise
+shortTitle: Unified search
+intro: 'You can allow users to include repositories on {% data variables.product.prodname_dotcom_the_website %} in their search results when searching from {% data variables.product.product_location %}.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /enterprise/admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-unified-search-between-github-enterprise-server-and-githubcom
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom
+permissions: 'Enterprise owners who are also owners of the connected {% data variables.product.prodname_ghe_cloud %} organization or enterprise account can enable unified search between {% data variables.product.product_name %} and {% data variables.product.prodname_dotcom_the_website %}.'
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - GitHub search
+---
+
+## {% data variables.product.prodname_unified_search %}について
+
+{% data reusables.github-connect.beta %}
+
+When you enable unified search, users can view search results from content on {% data variables.product.prodname_dotcom_the_website %} when searching from {% data variables.product.product_location %}{% ifversion ghae %} on {% data variables.product.prodname_ghe_managed %}{% endif %}.
+
+You can choose to allow search results for public repositories on {% data variables.product.prodname_dotcom_the_website %}, and you can separately choose to allow search results for private repositories on {% data variables.product.prodname_ghe_cloud %}. If you enable unified search for private repositories, users can only search private repositories that they have access to and that are owned by the connected organization or enterprise account. 詳細は「[{% data variables.product.prodname_dotcom %} での検索について](/search-github/getting-started-with-searching-on-github/about-searching-on-github/#searching-across-github-enterprise-and-githubcom-simultaneously)」を参照してください。
+
+Users will never be able to search {% data variables.product.product_location %} from {% data variables.product.prodname_dotcom_the_website %}, even if they have access to both environments.
+
+After you enable unified search for {% data variables.product.product_location %}, before individual users can see search results from {% data variables.product.prodname_dotcom_the_website %} on {% data variables.product.product_location %}, each user must also connect their personal account on {% data variables.product.product_name %} with a personal account on {% data variables.product.prodname_dotcom_the_website %}. For more information, see "[Enabling {% data variables.product.prodname_dotcom_the_website %} repository search in your private enterprise account](/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment)."
+
+REST及びGraphQL APIでの検索には、{% data variables.product.prodname_dotcom_the_website %}の検索結果は含まれません。 {% data variables.product.prodname_dotcom_the_website %}の高度な検索及びwikiの検索はサポートされていません。
+
+## {% data variables.product.prodname_unified_search %} の有効化
+
+Before you can enable {% data variables.product.prodname_unified_search %}, you must enable {% data variables.product.prodname_github_connect %}. For more information, see "[Managing {% data variables.product.prodname_github_connect %}](/admin/configuration/configuring-github-connect/managing-github-connect)."
+
+{% ifversion ghes %}
+{% data reusables.github-connect.access-dotcom-and-enterprise %}
+{% data reusables.enterprise_site_admin_settings.access-settings %}
+{% data reusables.enterprise_site_admin_settings.business %}
+{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. Sign into {% data variables.product.product_location %} and {% data variables.product.prodname_dotcom_the_website %}.
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. Under "Users can search {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![Enable search option in the [search GitHub.com] ドロップダウンメニューの [Enable search] オプション](/assets/images/enterprise/site-admin-settings/github-dotcom-enable-search.png)
+1. Optionally, under "Users can search private repositories on {% data variables.product.prodname_dotcom_the_website %}", use the drop-down menu and click **Enabled**. ![[search GitHub.com] ドロップダウンメニューの [Enable private repositories search] オプション](/assets/images/enterprise/site-admin-settings/enable-private-search.png)
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md
new file mode 100644
index 0000000000..8d195df5ff
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/index.md
@@ -0,0 +1,28 @@
+---
+title: Configuring GitHub Connect
+intro: 'With {% data variables.product.prodname_github_connect %}, you can access additional features and workflows by connecting {% data variables.product.product_location %} to {% data variables.product.prodname_ghe_cloud %}.'
+redirect_from:
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-to-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-and-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-and-github-com
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-and-githubcom
+  - /enterprise/admin/installation/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /enterprise/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+children:
+  - /about-github-connect
+  - /managing-github-connect
+  - /enabling-automatic-user-license-sync-for-your-enterprise
+  - /enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise
+  - /enabling-unified-search-for-your-enterprise
+  - /enabling-unified-contributions-for-your-enterprise
+shortTitle: GitHub Connect
+---
+
diff --git a/translations/ja-JP/content/admin/configuration/configuring-github-connect/managing-github-connect.md b/translations/ja-JP/content/admin/configuration/configuring-github-connect/managing-github-connect.md
new file mode 100644
index 0000000000..fda3921872
--- /dev/null
+++ b/translations/ja-JP/content/admin/configuration/configuring-github-connect/managing-github-connect.md
@@ -0,0 +1,81 @@
+---
+title: Managing GitHub Connect
+shortTitle: Manage GitHub Connect
+intro: 'You can enable {% data variables.product.prodname_github_connect %} to access additional features and workflows for {% data variables.product.product_location %}.'
+redirect_from:
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-to-github-com
+  - /enterprise/admin/guides/developer-workflow/connecting-github-enterprise-server-to-github-com
+  - /enterprise/admin/developer-workflow/connecting-github-enterprise-server-to-githubcom
+  - /enterprise/admin/installation/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /enterprise/admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/connecting-github-enterprise-server-to-github-enterprise-cloud
+  - /admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud
+versions:
+  ghes: '*'
+  ghae: '*'
+type: how_to
+topics:
+  - Enterprise
+  - GitHub Connect
+  - Infrastructure
+  - Networking
+---
+
+{% data reusables.github-connect.beta %}
+
+## {% data variables.product.prodname_github_connect %} について
+
+You can access additional features and workflows on {% data variables.product.product_location %} by enabling {% data variables.product.prodname_github_connect %}. 詳しい情報については、「[{% data variables.product.prodname_github_connect %} について](/admin/configuration/configuring-github-connect/about-github-connect)」を参照してください。
+
+When you enable {% data variables.product.prodname_github_connect %}, you configure a connection between {% data variables.product.product_location %} and an organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. Enabling {% data variables.product.prodname_github_connect %} creates a {% data variables.product.prodname_github_app %} owned by the organization or enterprise account on {% data variables.product.prodname_ghe_cloud %}. {% data variables.product.product_name %} は {% data variables.product.prodname_github_app %} のクレデンシャルを使って {% data variables.product.prodname_ghe_cloud %} へのリクエストを発行します。
+
+{% ifversion ghes %}
+{% data variables.product.prodname_ghe_server %} は {% data variables.product.prodname_github_app %} からのクレデンシャルを保存します。 The following credentials will be replicated to all nodes in a high availability or cluster environment, and stored in any backups, including snapshots created by {% data variables.product.prodname_enterprise_backup_utilities %}.
+- 1 時間にわたって有効な認証トークン
+- 新しい認証トークンを生成するのに使われる秘密鍵
+{% endif %}
+
+## 必要な環境
+
+To use {% data variables.product.prodname_github_connect %}, you must have an organization or enterprise account on {% data variables.product.prodname_dotcom_the_website %} that uses {% data variables.product.prodname_ghe_cloud %}. You may already have {% data variables.product.prodname_ghe_cloud %} included in your plan. {% data reusables.enterprise.link-to-ghec-trial %}
+
+{% ifversion ghes %}
+To configure a connection, your proxy configuration must allow connectivity to `github.com`, `api.github.com`, and `uploads.github.com`. 詳細は「[アウトバウンド Web プロキシサーバーを設定する](/enterprise/{{ currentVersion }}/admin/guides/installation/configuring-an-outbound-web-proxy-server)」を参照してください。
+{% endif %}
+
+## {% data variables.product.prodname_github_connect %} の有効化
+
+Enterprise owners who are also owners of an organization or enterprise account that uses {% data variables.product.prodname_ghe_cloud %} can enable {% data variables.product.prodname_github_connect %}.
+
+If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is not owned by an enterprise account, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an organization owner.
+
+If you're connecting {% data variables.product.product_location %} to an organization on {% data variables.product.prodname_ghe_cloud %} that is owned by an enterprise account or to an enterprise account itself, you must sign into {% data variables.product.prodname_dotcom_the_website %} as an enterprise owner.
+
+{% ifversion ghes %}
+1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。
+{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}{% else %}
+1. {% data variables.product.product_location %}と{% data variables.product.prodname_dotcom_the_website %}にサインインしてください。
+{% data reusables.enterprise-accounts.access-enterprise %}{% data reusables.enterprise-accounts.github-connect-tab %}{% endif %}
+1. 「{% data variables.product.prodname_github_connect %} is not enabled yet」の下で、「**Enable{% data variables.product.prodname_github_connect %}**」をクリックします。 By clicking **Enable {% data variables.product.prodname_github_connect %}**, you agree to the "<a href="/github/site-policy/github-terms-for-additional-products-and-features#connect" class="dotcom-only">{% data variables.product.prodname_dotcom %} Terms for Additional Products and Features</a>."
+{% ifversion ghes %}
+![Enable GitHub Connect button](/assets/images/enterprise/business-accounts/enable-github-connect-button.png){% else %}
+![Enable GitHub Connect button](/assets/images/enterprise/github-ae/enable-github-connect-button.png)
+{% endif %}
+1. 接続したいEnterpriseアカウントまたはOrganizationの横にある「**Connect**」をクリックします。 ![Enterprise アカウントまたはビジネスアカウントの横にある [Connect] ボタン](/assets/images/enterprise/business-accounts/choose-enterprise-or-org-connect.png)
+
+## {% data variables.product.prodname_github_connect %} を無効にする
+
+Enterprise owners can disable {% data variables.product.prodname_github_connect %}.
+
+{% data variables.product.prodname_ghe_cloud %}から切断すると、EnterpriseアカウントまたはOrganizationから{% data variables.product.prodname_github_connect %}{% data variables.product.prodname_github_app %}が削除され、{% data variables.product.product_location %}に保存されているクレデンシャルが削除されます。
+
+{% data reusables.enterprise-accounts.access-enterprise %}{% ifversion ghes < 3.1 %}{% data reusables.enterprise-accounts.settings-tab %}{% endif %}{% data reusables.enterprise-accounts.github-connect-tab %}
+1. 切断しようとするEnterpriseアカウントまたはOrganizationの横にある「**Disable {% data variables.product.prodname_github_connect %}**」をクリックします。
+{% ifversion ghes %}
+  ![EnterpriseアカウントまたはOrganization名の横にある「Disable GitHub Connect」ボタン](/assets/images/enterprise/business-accounts/disable-github-connect-button.png)
+1. 切断に関する情報を読み、「 **Disable {% data variables.product.prodname_github_connect %}**」をクリックします。 ![切断に関する警告情報が表示され確定ボタンがあるモーダル](/assets/images/enterprise/business-accounts/confirm-disable-github-connect.png)
+{% else %}
+  ![EnterpriseアカウントまたはOrganization名の横にある「Disable GitHub Connect」ボタン](/assets/images/enterprise/github-ae/disable-github-connect-button.png)
+1. 切断に関する情報を読み、「 **Disable {% data variables.product.prodname_github_connect %}**」をクリックします。 ![切断に関する警告情報が表示され確定ボタンがあるモーダル](/assets/images/enterprise/github-ae/confirm-disable-github-connect.png)
+{% endif %} 
diff --git a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
index f18aca0be0..e842fc8ab5 100644
--- a/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
+++ b/translations/ja-JP/content/admin/configuration/configuring-your-enterprise/configuring-custom-footers.md
@@ -4,6 +4,7 @@ intro: 'You can give users easy access to enterprise-specific links by adding cu
 versions:
   ghec: '*'
   ghes: '>=3.4'
+  ghae: issue-5487
 type: how_to
 topics:
   - Enterprise
@@ -15,7 +16,7 @@ Enterprise owners can configure {% data variables.product.product_name %} to sho
 
 ![Custom footer](/assets/images/enterprise/custom-footer/octodemo-footer.png)
 
-The custom footer is displayed above the {% data variables.product.prodname_dotcom %} footer {% ifversion ghes or ghae %}to all users, on all pages of {% data variables.product.product_name %}{% else %}to all enterprise members and collaborators, on all repository and organization pages for repositories and organizations that belong to the enterprise{% endif %}.
+The custom footer is displayed above the {% data variables.product.prodname_dotcom %} footer {% ifversion ghes or ghae %}to all users, on all pages of {% data variables.product.product_name %}{% elsif ghec %}to all enterprise members and collaborators, on all repository and organization pages for repositories and organizations that belong to the enterprise{% endif %}.
 
 ## Configuring custom footers for your enterprise
 
diff --git a/translations/ja-JP/content/admin/configuration/index.md b/translations/ja-JP/content/admin/configuration/index.md
index 9aea08c87f..3c86acd480 100644
--- a/translations/ja-JP/content/admin/configuration/index.md
+++ b/translations/ja-JP/content/admin/configuration/index.md
@@ -13,7 +13,7 @@ topics:
 children:
   - /configuring-your-enterprise
   - /configuring-network-settings
-  - /managing-connections-between-your-enterprise-accounts
+  - /configuring-github-connect
 ---
 
 {% ifversion ghes %}
diff --git a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
index 936c7024f1..ab7b495038 100644
--- a/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
+++ b/translations/ja-JP/content/admin/github-actions/enabling-github-actions-for-github-enterprise-server/setting-up-dependabot-updates.md
@@ -37,7 +37,7 @@ Both types of {% data variables.product.prodname_dependabot %} update have the f
 - Configure {% data variables.product.product_location %} to use {% data variables.product.prodname_actions %}. For more information, see "[Getting started with {% data variables.product.prodname_actions %} for GitHub Enterprise Server](/admin/github-actions/enabling-github-actions-for-github-enterprise-server/getting-started-with-github-actions-for-github-enterprise-server)."
 - Set up one or more {% data variables.product.prodname_actions %} self-hosted runners for {% data variables.product.prodname_dependabot %}. For more information, see "[Setting up self-hosted runners for {% data variables.product.prodname_dependabot %} updates](#setting-up-self-hosted-runners-for-dependabot-updates)" below.
 
-Additionally, {% data variables.product.prodname_dependabot_security_updates %} rely on the dependency graph, vulnerability data from {% data variables.product.prodname_github_connect %}, and {% data variables.product.prodname_dependabot_alerts %}. These features must be enabled on {% data variables.product.product_location %}. For more information, see "[Enabling the dependency graph and  {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Additionally, {% data variables.product.prodname_dependabot_security_updates %} rely on the dependency graph, vulnerability data from {% data variables.product.prodname_github_connect %}, and {% data variables.product.prodname_dependabot_alerts %}. These features must be enabled on {% data variables.product.product_location %}. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 
 ## Setting up self-hosted runners for {% data variables.product.prodname_dependabot %} updates
 
diff --git a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
index f0f28b2088..07d53a87c4 100644
--- a/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/github-actions/getting-started-with-github-actions-for-your-enterprise/introducing-github-actions-to-your-enterprise.md
@@ -32,7 +32,7 @@ Then,{% else %}First,{% endif %} decide whether you'll allow third-party actions
 
 ![Screenshot of {% data variables.product.prodname_actions %} policies](/assets/images/help/organizations/enterprise-actions-policy.png)
 
-{% ifversion ghec or ghae-issue-4757-and-5856 %}
+{% ifversion ghec or ghae-issue-4757 %}
 Consider combining OpenID Connect (OIDC) with reusable workflows to enforce consistent deployments across your repository, organization, or enterprise. You can do this by defining trust conditions on cloud roles based on reusable workflows. For more information, see "[Using OpenID Connect with reusable workflows](/actions/deployment/security-hardening-your-deployments/using-openid-connect-with-reusable-workflows)."
 {% endif %}
 
@@ -66,7 +66,9 @@ There is significant risk in sourcing actions from third-party repositories on {
 
 ## Innersourcing
 
-Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource workflows. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
+Think about how your enterprise can use features of {% data variables.product.prodname_actions %} to innersource automation. Innersourcing is a way to incorporate the benefits of open source methodologies into your internal software development cycle. For more information, see [An introduction to innersource](https://resources.github.com/whitepapers/introduction-to-innersource/) in {% data variables.product.company_short %} Resources.
+
+{% data reusables.actions.internal-actions-summary %}
 
 {% ifversion ghec or ghes > 3.3 or ghae-issue-4757 %}
 With reusable workflows, your team can call one workflow from another workflow, avoiding exact duplication. Reusable workflows promote best practice by helping your team use workflows that are well designed and have already been tested. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
@@ -74,7 +76,9 @@ With reusable workflows, your team can call one workflow from another workflow,
 
 To provide a starting place for developers building new workflows, you can use starter workflows. This not only saves time for your developers, but promotes consistency and best practice across your enterprise. For more information, see "[Creating starter workflows for your organization](/actions/learn-github-actions/creating-starter-workflows-for-your-organization)."
 
+{% if not internal-actions %}
 Whenever your workflow developers want to use an action that's stored in a private repository, they must configure the workflow to clone the repository first. To reduce the number of repositories that must be cloned, consider grouping commonly used actions in a single repository. For more information, see "[About custom actions](/actions/creating-actions/about-custom-actions#choosing-a-location-for-your-action)."
+{% endif %}
 
 ## Managing resources
 
diff --git a/translations/ja-JP/content/admin/guides.md b/translations/ja-JP/content/admin/guides.md
index 488b35c461..373ad73e69 100644
--- a/translations/ja-JP/content/admin/guides.md
+++ b/translations/ja-JP/content/admin/guides.md
@@ -53,11 +53,11 @@ includeGuides:
   - /admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise
   - /admin/configuration/connecting-your-enterprise-account-to-github-enterprise-cloud
   - /admin/configuration/enabling-and-scheduling-maintenance-mode
-  - /admin/configuration/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud
+  - /admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise
   - /admin/configuration/enabling-private-mode
   - /admin/configuration/enabling-subdomain-isolation
-  - /admin/configuration/enabling-unified-contributions-between-your-enterprise-account-and-githubcom
-  - /admin/configuration/enabling-unified-search-between-your-enterprise-account-and-githubcom
+  - /admin/configuration/configuring-github-connect/enabling-unified-contributions-for-your-enterprise
+  - /admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise
   - /admin/configuration/initializing-github-ae
   - /admin/configuration/network-ports
   - /admin/configuration/restricting-network-traffic-to-your-enterprise
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
index d52f1213c4..06a647f299 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/adding-organizations-to-your-enterprise.md
@@ -45,6 +45,6 @@ Enterprise owners can invite existing organizations to join their enterprise acc
 2. On the **Organizations** tab, above the list of organizations, click **Invite organization**. ![Invite organization](/assets/images/help/business-accounts/enterprise-account-invite-organization.png)
 3. Under "Organization name", start typing the name of the organization you want to invite and select it when it appears in the drop-down list. ![Search for organization](/assets/images/help/business-accounts/enterprise-account-search-for-organization.png)
 4. Click **Invite organization**.
-5. The organization owners will receive an email inviting them to join the organization. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
+5. The organization owners will receive an email inviting them to join the enterprise. At least one owner needs to accept the invitation before the process can continue. You can cancel or resend the invitation at any time before an owner approves it. ![Cancel or resend](/assets/images/help/business-accounts/enterprise-account-invitation-sent.png)
 6. Once an organization owner has approved the invitation, you can view its status in the list of pending invitations. ![Pending invitation](/assets/images/help/business-accounts/enterprise-account-pending.png)
 7. Click **Approve** to complete the transfer, or **Cancel** to cancel it. ![Approve invitation](/assets/images/help/business-accounts/enterprise-account-transfer-approve.png)
diff --git a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
index 5ddba0ed11..89cb36c878 100644
--- a/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
+++ b/translations/ja-JP/content/admin/user-management/managing-organizations-in-your-enterprise/streaming-the-audit-logs-for-organizations-in-your-enterprise-account.md
@@ -16,12 +16,6 @@ redirect_from:
 permissions: Enterprise owners can configure audit log streaming.
 ---
 
-{% note %}
-
-**Note:** Audit log streaming is currently in beta for {% data variables.product.prodname_ghe_cloud %} and subject to change.
-
-{% endnote %}
-
 ## About exporting audit data
 
 You can extract audit log and Git events data from {% data variables.product.prodname_dotcom %} in multiple ways:
@@ -32,6 +26,7 @@ You can extract audit log and Git events data from {% data variables.product.pro
 
 Currently, audit log streaming is supported for multiple storage providers.
 - Amazon S3
+- Azure Blob Storage
 - Azure Event Hubs
 - Google Cloud Storage
 - Splunk
@@ -54,7 +49,8 @@ Enterprise owners can set up, pause, or delete a stream at any time. The stream
 You set up the audit log stream on {% data variables.product.product_name %} by following the instructions for your provider.
 
 - [Amazon S3](#setting-up-streaming-to-amazon-s3)
-- [Azure Event Hubs](#setting-up-streaming-to-splunk)
+- [Azure Blob Storage](#setting-up-streaming-to-azure-blob-storage)
+- [Azure Event Hubs](#setting-up-streaming-to-azure-event-hubs)
 - [Google Cloud Storage](#setting-up-streaming-to-google-cloud-storage)
 - [Splunk](#setting-up-streaming-to-splunk)
 
@@ -70,12 +66,62 @@ To set up audit log streaming from {% data variables.product.prodname_dotcom %}
 For information on creating or accessing your access key ID and secret key, see [Understanding and getting your AWS credentials](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html) in the AWS documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Amazon S3**. ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+1. Click **Configure stream** and select **Amazon S3**.
+
+   ![Choose Amazon S3 from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-s3.png)
+
 1. On the configuration page, enter:
    * The name of the bucket you want to stream to. For example, `auditlog-streaming-test`.
    * Your access key ID. For example, `ABCAIOSFODNN7EXAMPLE1`.
-   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Amazon S3 endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * Your secret key. For example, `aBcJalrXUtnWXYZ/A1MDENG/zPxRfiCYEXAMPLEKEY`.
+
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-s3.png)
+
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Amazon S3 endpoint.
+
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+
+{% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
+
+### Setting up streaming to Azure Blob Storage
+
+Before setting up a stream in {% data variables.product.prodname_dotcom %}, you must first have created a storage account and a container in Microsoft Azure. For details, see the Microsoft documentation, "[Introduction to Azure Blob Storage](https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blobs-introduction)."
+
+To configure the stream in {% data variables.product.prodname_dotcom %} you need the URL of a SAS token.
+
+**On Microsoft Azure portal**:
+1. On the Home page, click **Storage Accounts**.
+2. Click the name of the storage account you want to use, then click **Containers**.
+
+   ![The Containers link in Azure](/assets/images/azure/azure-storage-containers.png)
+
+1. Click the name of the container you want to use.
+1. Click **Shared access tokens**.
+
+   ![The shared access token link in Azure](/assets/images/azure/azure-storage-shared-access-tokens.png)
+
+1. In the **Permissions** drop-down menu, change the permissions to only allow `Create` and `Write`.
+
+   ![The permissions drop-down menu](/assets/images/azure/azure-storage-permissions.png)
+
+1. Set an expiry date that complies with your secret rotation policy.
+1. Click **Generate SAS token and URL**.
+1. Copy the value of the **Blob SAS URL** field that's displayed. You will use this URL in {% data variables.product.prodname_dotcom %}.
+
+**On {% data variables.product.prodname_dotcom %}**:
+{% data reusables.enterprise.navigate-to-log-streaming-tab %}
+1. Click **Configure stream** and select **Azure Blob Storage**.
+
+   ![Choose Azure Blob Storage from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azureblob.png)
+
+1. On the configuration page, enter the blob SAS URL that you copied in Azure. The **Container** field is auto-filled based on the URL.
+
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azureblob.png)
+
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Blob Storage endpoint.
+
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Azure Event Hubs
@@ -85,19 +131,40 @@ Before setting up a stream in {% data variables.product.prodname_dotcom %}, you
 You need two pieces of information about your event hub: its instance name and the connection string.
 
 **On Microsoft Azure portal**:
-1. In the left menu select **Entities**. Then select **Event Hubs**. The names of your event hubs are listed. ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
+1. Search for "Event Hubs".
+
+   ![The Azure portal search box](/assets/images/azure/azure-resources-search.png)
+
+1. Select **Event Hubs**. The names of your event hubs are listed.
+
+   ![A list of event hubs](/assets/images/help/enterprises/azure-event-hubs-list.png)
+
 1. Make a note of the name of the event hub you want to stream to.
 1. Click the required event hub. Then, in the left menu, select **Shared Access Policies**.
-1. Select a shared access policy in the list of policies, or create a new policy. ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
-1. Click the button to the right of the **Connection string-primary key** field to copy the connection string. ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
+1. Select a shared access policy in the list of policies, or create a new policy.
+
+   ![A list of shared access policies](/assets/images/help/enterprises/azure-shared-access-policies.png)
+
+1. Click the button to the right of the **Connection string-primary key** field to copy the connection string.
+
+   ![The event hub connection string](/assets/images/help/enterprises/azure-connection-string.png)
 
 **On {% data variables.product.prodname_dotcom %}**:
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Azure Event Hubs**. ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+1. Click **Configure stream** and select **Azure Event Hubs**.
+
+   ![Choose Azure Events Hub from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-azure.png)
+
 1. On the configuration page, enter:
    * The name of the Azure Event Hubs instance.
-   * The connection string. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Azure endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+   * The connection string.
+
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-azure.png)
+
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Azure Events Hub endpoint.
+
+   ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check.png)
+
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ### Setting up streaming to Google Cloud Storage
@@ -132,7 +199,10 @@ To set up streaming to Google Cloud Storage, you must create a service account i
 To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must make sure that the endpoint is configured to accept HTTPS connections. For more information, see [Set up and use HTTP Event Collector in Splunk Web](https://docs.splunk.com/Documentation/Splunk/latest/Data/UsetheHTTPEventCollector) in the Splunk documentation.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Configure stream** and select **Splunk**. ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+1. Click **Configure stream** and select **Splunk**.
+
+   ![Choose Splunk from the drop-down menu](/assets/images/help/enterprises/audit-stream-choice-splunk.png)
+
 1. On the configuration page, enter:
    * The domain on which the application you want to stream to is hosted.
 
@@ -142,12 +212,14 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma
 
      If you are using Splunk Cloud, `Port` should be `443` if you haven't changed the port configuration. If you are using the free trial version of Splunk Cloud, `Port` should be `8088`.
 
-   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application. ![Enter stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
+   * A token that {% data variables.product.prodname_dotcom %} can use to authenticate to the third-party application.
+
+   ![Enter the stream settings](/assets/images/help/enterprises/audit-stream-add-splunk.png)
 
 1. Leave the **Enable SSL verification** check box selected.
 
     Audit logs are always streamed as encrypted data, however, with this option selected, {% data variables.product.prodname_dotcom %} verifies the SSL certificate of your Splunk instance when delivering events. SSL verification helps ensure that events are delivered to your URL endpoint securely. You can clear the selection of this option, but we recommend you leave SSL verification enabled.
-1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
+1. Click **Check endpoint** to verify that {% data variables.product.prodname_dotcom %} can connect and write to the Splunk endpoint. ![Check the endpoint](/assets/images/help/enterprises/audit-stream-check-splunk.png)
 {% data reusables.enterprise.verify-audit-log-streaming-endpoint %}
 
 ## Pausing audit log streaming
@@ -155,7 +227,10 @@ To stream audit logs to Splunk's HTTP Event Collector (HEC) endpoint you must ma
 Pausing the stream allows you to perform maintenance on the receiving application without losing audit data. Audit logs are stored for up to seven days on {% data variables.product.product_location %} and are then exported when you unpause the stream.
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Pause stream**. ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
+1. Click **Pause stream**.
+
+   ![Pause the stream](/assets/images/help/enterprises/audit-stream-pause.png)
+
 1. A confirmation message is displayed. Click **Pause stream** to confirm.
 
 When the application is ready to receive audit logs again, click **Resume stream** to restart streaming audit logs.
@@ -163,5 +238,8 @@ When the application is ready to receive audit logs again, click **Resume stream
 ## Deleting the audit log stream
 
 {% data reusables.enterprise.navigate-to-log-streaming-tab %}
-1. Click **Delete stream**. ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
-2. A confirmation message is displayed. Click **Delete stream** to confirm.
+1. Click **Delete stream**.
+
+   ![Delete the stream](/assets/images/help/enterprises/audit-stream-delete.png)
+
+1. A confirmation message is displayed. Click **Delete stream** to confirm.
diff --git a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
index ee5d2818e4..42f322522b 100644
--- a/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
+++ b/translations/ja-JP/content/admin/user-management/managing-users-in-your-enterprise/impersonating-a-user.md
@@ -4,6 +4,7 @@ intro: 'You can impersonate users and perform actions on their behalf, for troub
 permissions: Enterprise owners can impersonate users within their enterprise.
 versions:
   ghes: '>3.2'
+  ghae: '*'
 type: how_to
 topics:
   - Administrator
diff --git a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
index a9b090aaf9..a8ce337232 100644
--- a/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
+++ b/translations/ja-JP/content/admin/user-management/monitoring-activity-in-your-enterprise/audited-actions.md
@@ -133,14 +133,14 @@ topics:
 
 ## サイトアドミンのツール
 
-| アクション                   | 説明                                                                                             |
-| ----------------------- | ---------------------------------------------------------------------------------------------- |
-| `staff.disable_repo`    | サイトアドミンがリポジトリとその全てのフォークへのアクセスを無効にしました。                                                         |
-| `staff.enable_repo`     | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghes > 3.2 %}
-| `staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}.      |
+| アクション                   | 説明                                                                                                     |
+| ----------------------- | ------------------------------------------------------------------------------------------------------ |
+| `staff.disable_repo`    | サイトアドミンがリポジトリとその全てのフォークへのアクセスを無効にしました。                                                                 |
+| `staff.enable_repo`     | A site admin re-enabled access to a repository and all of its forks.{% ifversion ghae or ghes > 3.2 %}
+| `staff.exit_fake_login` | A site admin ended an impersonation session on {% data variables.product.product_name %}.              |
 | `staff.fake_login`      | A site admin signed into {% data variables.product.product_name %} as another user.{% endif %}
-| `staff.repo_unlock`     | サイトアドミンがユーザのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                                 |
-| `staff.unlock`          | サイトアドミンがユーザの全てのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                              |
+| `staff.repo_unlock`     | サイトアドミンがユーザのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                                         |
+| `staff.unlock`          | サイトアドミンがユーザの全てのプライベートリポジトリを解除（一時的にフルアクセスが可能）しました。                                                      |
 
 ## Team
 
diff --git a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
index 0426103077..3c98069a99 100644
--- a/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
+++ b/translations/ja-JP/content/billing/managing-your-license-for-github-enterprise/syncing-license-usage-between-github-enterprise-server-and-github-enterprise-cloud.md
@@ -22,7 +22,7 @@ For more information about licenses and usage for {% data variables.product.prod
 
 ## Automatically syncing license usage
 
-{% data variables.product.prodname_github_connect %}を使用して、{% data variables.product.prodname_ghe_server %}と{% data variables.product.prodname_ghe_cloud %}の間でユーザライセンスの数と使用状況を自動で同期できます。 For more information, see "[Enabling automatic user license sync between {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-github-enterprise-server-and-github-enterprise-cloud/enabling-automatic-user-license-sync-between-github-enterprise-server-and-github-enterprise-cloud){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
+{% data variables.product.prodname_github_connect %}を使用して、{% data variables.product.prodname_ghe_server %}と{% data variables.product.prodname_ghe_cloud %}の間でユーザライセンスの数と使用状況を自動で同期できます。 For more information, see "[Enabling automatic user license sync for your enterprise]({% ifversion ghec %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-automatic-user-license-sync-for-your-enterprise){% ifversion ghec %}" in the {% data variables.product.prodname_ghe_server %} documentation.{% elsif ghes %}."{% endif %}
 
 ## Manually syncing license usage
 
diff --git a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
index 124f373559..a8ee0d45df 100644
--- a/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
+++ b/translations/ja-JP/content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/troubleshooting-the-codeql-workflow.md
@@ -42,7 +42,7 @@ topics:
 
 You can obtain artifacts to help you debug {% data variables.product.prodname_codeql %} by setting a debug configuration flag. Modify the `init` step of your {% data variables.product.prodname_codeql %} workflow file and set `debug: true`.
 
-```
+```yaml
 - name: Initialize CodeQL
   uses: github/codeql-action/init@v1
   with:
@@ -140,11 +140,11 @@ Replace the `autobuild` step with the same build commands you would use in produ
 
 ### Inspect the copy of the source files in the {% data variables.product.prodname_codeql %} database
 You may be able to understand why some source files haven't been analyzed by inspecting the copy of the source code included with the {% data variables.product.prodname_codeql %} database. To obtain the database from your Actions workflow, add an `upload-artifact` action after the analysis step in your code scanning workflow:
-```
+```yaml
 - uses: actions/upload-artifact@v2
   with:
-    name: codeql-database
-    path: ../codeql-database
+    name: {% raw %}codeql-database-${{ matrix.language }}{% endraw %}
+    path: {% raw %}${{ runner.temp }}/codeql_databases{% endraw %}
 ```
 This uploads the database as an actions artifact that you can download to your local machine. For more information, see "[Storing workflow artifacts](/actions/guides/storing-workflow-data-as-artifacts)."
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
index 615b883990..6103dc03ca 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/managing-vulnerabilities-in-your-projects-dependencies/configuring-notifications-for-vulnerable-dependencies.md
@@ -33,7 +33,7 @@ topics:
 {% ifversion ghes or ghae-issue-4864 %}
 By default, if your enterprise owner has configured email for notifications on your enterprise, you will receive {% data variables.product.prodname_dependabot_alerts %} by email.
 
-Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Enterprise owners can also enable {% data variables.product.prodname_dependabot_alerts %} without notifications. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 {% endif %}
 
 ## {% data variables.product.prodname_dependabot_alerts %}の通知設定
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
index 80eaba073f..4cc8e5b8c8 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-dependency-review.md
@@ -38,7 +38,7 @@ Dependency review is available when dependency graph is enabled for {% data vari
 
 時に、マニフェスト内の 1 つの依存関係のバージョンを更新して、プルリクエストを生成することがあります。 ただし、この直接依存関係の更新バージョンでも依存関係が更新されている場合は、プルリクエストに予想よりも多くの変更が加えられている可能性があります。 各マニフェストとロックファイルの依存関係のレビューにより、何が変更されたか、新しい依存関係バージョンのいずれかに既知の脆弱性が含まれているかどうかを簡単に確認できます。
 
-プルリクエストで依存関係のレビューを確認し、脆弱性としてフラグが付けられている依存関係を変更することで、プロジェクトに脆弱性が追加されるのを防ぐことができます。 For more information about how dependency review works, see "[Reviewing dependency changes in a pull request](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)."
+プルリクエストで依存関係のレビューを確認し、脆弱性としてフラグが付けられている依存関係を変更することで、プロジェクトに脆弱性が追加されるのを防ぐことができます。 依存関係のレビューの動作に関する詳しい情報については「[Pull Request中の依存関係の変更のレビュー](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/incorporating-feedback-in-your-pull-request)」を参照してください。
 
 {% data variables.product.prodname_dependabot_alerts %} は、すでに依存関係にある脆弱性を検出しますが、あとで修正するよりも、潜在的な問題が持ち込まれることを回避する方がはるかに良いです。 {% data variables.product.prodname_dependabot_alerts %} に関する詳しい情報については、「[脆弱性のある依存関係に対するアラートについて](/github/managing-security-vulnerabilities/about-alerts-for-vulnerable-dependencies#dependabot-alerts-for-vulnerable-dependencies)」を参照してください。
 
@@ -46,4 +46,4 @@ Dependency review is available when dependency graph is enabled for {% data vari
 
 ## Enabling dependency review
 
-The dependency review feature becomes available when you enable the dependency graph. {% ifversion fpt or ghec %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}For more information, see "[Enabling the dependency graph and Dependabot alerts on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %}
+The dependency review feature becomes available when you enable the dependency graph. {% ifversion fpt or ghec %}For more information, see "[Enabling the dependency graph](/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph#enabling-the-dependency-graph)."{% endif %}{% ifversion ghes or ghae %}For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."{% endif %}
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
index 14ea4e4b20..716a544e20 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/about-the-dependency-graph.md
@@ -65,7 +65,7 @@ You can use the dependency graph to:
 
 {% ifversion fpt or ghec %}To generate a dependency graph, {% data variables.product.product_name %} needs read-only access to the dependency manifest and lock files for a repository. The dependency graph is automatically generated for all public repositories and you can choose to enable it for private repositories. For information about enabling or disabling it for private repositories, see "[Exploring the dependencies of a repository](/github/visualizing-repository-data-with-graphs/exploring-the-dependencies-of-a-repository)."{% endif %}
 
-{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see  "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."{% endif %}
+{% ifversion ghes or ghae %}If the dependency graph is not available in your system, your enterprise owner can enable the dependency graph and {% data variables.product.prodname_dependabot_alerts %}. For more information, see  "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."{% endif %}
 
 When the dependency graph is first enabled, any manifest and lock files for supported ecosystems are parsed immediately. The graph is usually populated within minutes but this may take longer for repositories with many dependencies. Once enabled, the graph is automatically updated with every push to the repository{% ifversion fpt or ghec %} and every push to other repositories in the graph{% endif %}.
 
diff --git a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
index 51dfecd806..554db3484e 100644
--- a/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
+++ b/translations/ja-JP/content/code-security/supply-chain-security/understanding-your-software-supply-chain/exploring-the-dependencies-of-a-repository.md
@@ -34,7 +34,7 @@ shortTitle: 依存関係の調査
 4. オプションとして、[Dependency graph] で [**Dependents**] をクリックします。 ![Dependents tab on the dependency graph page](/assets/images/help/graphs/dependency-graph-dependents-tab.png){% endif %}
 
 {% ifversion ghes or ghae-issue-4864 %}
-Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+Enterprise owners can configure the dependency graph at an enterprise level. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 {% endif %}
 
 ### 依存関係ビュー
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
index c42aaee27e..1014f87181 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository.md
@@ -37,7 +37,7 @@ shortTitle: リポジトリへのライセンスの追加
 {% endif %}
 
 <!--GHE version just adds a file named LICENSE or LICENSE.md-->
-{% ifversion ghes or ghae %}
+{% ifversion ghes %}
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.files.add-file %}
diff --git a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
index 8941ffef91..3eaa6e1862 100644
--- a/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
+++ b/translations/ja-JP/content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md
@@ -23,20 +23,20 @@ You can add default community health files to a public repository called `.githu
 - the `.github` folder
 - the `docs` folder
 
-For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghae or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
+For example, anyone who creates an issue or pull request in a repository that does not have its own CONTRIBUTING file will see a link to the default CONTRIBUTING file. If a repository has any files in its own `.github/ISSUE_TEMPLATE` folder{% ifversion fpt or ghes or ghec %}, including issue templates or a *config.yml* file,{% endif %} none of the contents of the default `.github/ISSUE_TEMPLATE` folder will be used.
 
 Default files are not included in clones, packages, or downloads of individual repositories because they are stored only in the `.github` repository.
 
 ## Supported file types
 
-You can create defaults in your organization{% ifversion fpt or ghae or ghes or ghec %} or user account{% endif %} for the following community health files:
+You can create defaults in your organization{% ifversion fpt or ghes or ghec %} or user account{% endif %} for the following community health files:
 
 Community health file | Description
 --- | ---{% ifversion fpt or ghec %}
 *CODE_OF_CONDUCT.md* | A CODE_OF_CONDUCT file defines standards for how to engage in a community. For more information, see "[Adding a code of conduct to your project](/articles/adding-a-code-of-conduct-to-your-project/)."{% endif %}
 *CONTRIBUTING.md* | A CONTRIBUTING file communicates how people should contribute to your project. For more information, see "[Setting guidelines for repository contributors](/articles/setting-guidelines-for-repository-contributors/)."{% ifversion fpt or ghec %}
 *FUNDING.yml* | A FUNDING file displays a sponsor button in your repository to increase the visibility of funding options for your open source project. For more information, see "[Displaying a sponsor button in your repository](/articles/displaying-a-sponsor-button-in-your-repository)."{% endif %}
-Issue and pull request templates{% ifversion fpt or ghae or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes > 3.0 or ghec %}
+Issue and pull request templates{% ifversion fpt or ghes or ghec %} and *config.yml*{% endif %} | Issue and pull request templates customize and standardize the information you'd like contributors to include when they open issues and pull requests in your repository. For more information, see "[About issue and pull request templates](/articles/about-issue-and-pull-request-templates/)."{% ifversion fpt or ghes > 3.0 or ghec %}
 *SECURITY.md* | A SECURITY file gives instructions for how to report a security vulnerability in your project. For more information, see "[Adding a security policy to your repository](/code-security/getting-started/adding-a-security-policy-to-your-repository)."{% endif %}
 *SUPPORT.md* | A SUPPORT file lets people know about ways to get help with your project. For more information, see "[Adding support resources to your project](/articles/adding-support-resources-to-your-project/)."
 
@@ -45,7 +45,7 @@ You cannot create a default license file. License files must be added to individ
 ## Creating a repository for default files
 
 {% data reusables.repositories.create_new %}
-2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghae or ghes or ghec %} or user account{% endif %} you want to create default files for.
+2. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or user account{% endif %} you want to create default files for.
   ![Owner drop-down menu](/assets/images/help/repository/create-repository-owner.png)
 3. Type **.github** as the name for your repository, and an optional description.
   ![Create repository field](/assets/images/help/repository/default-file-repository-name.png)
@@ -53,4 +53,4 @@ You cannot create a default license file. License files must be added to individ
   ![Radio buttons to select private or public status](/assets/images/help/repository/create-repository-public-private.png)
 {% data reusables.repositories.initialize-with-readme %}
 {% data reusables.repositories.create-repo %}
-7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghae or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
+7. In the repository, create one of the supported community health files. Issue templates{% ifversion fpt or ghes or ghec %} and their configuration file{% endif %} must be in a folder called `.github/ISSUE_TEMPLATE`. All other supported files may be in the root of the repository, the `.github` folder, or the `docs` folder. For more information, see "[Creating new files](/articles/creating-new-files/)."
diff --git a/translations/ja-JP/content/developers/overview/replacing-github-services.md b/translations/ja-JP/content/developers/overview/replacing-github-services.md
index ef9fda4c42..33ad13af51 100644
--- a/translations/ja-JP/content/developers/overview/replacing-github-services.md
+++ b/translations/ja-JP/content/developers/overview/replacing-github-services.md
@@ -32,7 +32,7 @@ GitHub Servicesは、webhookとの統合を進めるために非推奨となり
 
 GitHub Services（Service Hooksと呼ばれることもあります）は、インテグレーションの旧来の方法であり、GitHubがインテグレーターのサービスの一部を[`github-services`リポジトリ](https://github.com/github/github-services)を通じてホストします。 GitHub上で行われたアクションがこれらのサービスをトリガーし、これらのサービスを使ってGitHubの外部のアクションをトリガーできます。
 
-{% ifversion ghes or ghae %}
+{% ifversion ghes %}
 ## GitHub Servicesを使っているリポジトリを探す
 アプライアンス上でどのリポジトリがGitHub Servicesを使っているかを特定するためのコマンドラインスクリプトが提供されています。 詳しい情報については[ghe-legacy-github-services-report](/enterprise/{{currentVersion}}/admin/articles/command-line-utilities/#ghe-legacy-github-services-report)を参照してください。{% endif %}
 
diff --git a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
index 916ac237df..b2e05b0d26 100644
--- a/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
+++ b/translations/ja-JP/content/get-started/using-github/keyboard-shortcuts.md
@@ -98,7 +98,7 @@ The {% data variables.product.prodname_command_palette %} also gives you quick a
 | <kbd>control shift p</kbd> または <kbd>command shift p</kbd> | Toggles between the **Write** and **Preview** comment tabs{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 | <kbd>control shift 7</kbd> or <kbd>command shift 7</kbd>  | Inserts Markdown formatting for an ordered list                                                                                                                                                 |
 | <kbd>control shift 8</kbd> or <kbd>command shift 8</kbd>  | Inserts Markdown formatting for an unordered list{% endif %}
-| <kbd>control enter</kbd>                                  | コメントをサブミットします                                                                                                                                                                                   |
+| <kbd>control enter</kbd> or <kbd>command enter</kbd>      | コメントをサブミットします                                                                                                                                                                                   |
 | <kbd>control .</kbd>、次に <kbd>control [返信テンプレート番号]</kbd>   | 返信テンプレートメニューを開き、コメントフィールドに返信テンプレートを自動入力します。 詳細は「[返信テンプレートについて](/articles/about-saved-replies)」を参照してください。{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
 | <kbd>control shift .</kbd> or <kbd>command shift.</kbd>   | Inserts Markdown formatting for a quote{% endif %}{% ifversion fpt or ghec %}
 | <kbd>control g</kbd> または <kbd>command g</kbd>             | 提案を挿入します。 詳細は「[プルリクエストで提案された変更をレビューする](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/reviewing-proposed-changes-in-a-pull-request)」を参照してください。 
diff --git a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
index 1bdf1c69ad..0d2c329722 100644
--- a/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
+++ b/translations/ja-JP/content/github/site-policy/github-terms-for-additional-products-and-features.md
@@ -20,7 +20,7 @@ GitHub を利用する際、数多くの追加製品や機能 (「追加製品
 
 - **GitHub Enterprise Server** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Learning Lab, Packages, Pages, and SQL Server Images.
 
-- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, {% ifversion ghae %}Connect, {% endif %}Dependabot Preview, GitHub Enterprise Importer, Packages and Pages.
+- **GitHub AE** users may have access to the following Additional Products and Features: Actions, Advanced Security, Advisory Database, Connect, Dependabot Preview, GitHub Enterprise Importer, Packages and Pages.
 
 ## アクション
 GitHubアクションでは、カスタムソフトウェア開発のライフサイクルにわたるワークフローをGitHubリポジトリに直接作成することができます。 Actionsは、使用量に基づいて課金されます。 [Actionsのドキュメント](/actions)には、計算量やストレージ容量 (アカウントのプランによって異なる)、およびActionsの使用分数の監視方法や利用限度の設定方法などの詳細情報が記載されています。
@@ -68,7 +68,7 @@ Codespaces allows you to load extensions from the Microsoft Visual Studio Market
 The generally available version of Codespaces is not currently available for U.S. government customers. アメリカ合衆国の祝日 government customers may continue to use the Codespaces Beta Preview under separate terms. See [Beta Preview terms](/github/site-policy/github-terms-of-service#j-beta-previews).
 
 ## Connect
-GitHub Connect を使うと、GitHub Enterprise Server{% ifversion ghae %}やGitHub AE {% endif %}インスタンスとGitHub.comのGitHub Enterprise Cloud OrganizationまたはEnterpriseアカウントとの間で特定の機能やデータを共有できます。 GitHub Connectを有効化するには、GitHub Enterprise CloudまたはGitHub.comに最低1つのアカウントを持ち、GitHub Enterprise Server{% ifversion ghae %}またはGitHub AE{% endif %}の最低1つのライセンスインスタンスを持っている必要があります。 Connect経由でのGitHub Enterprise CloudまたはGitHub.comの利用は、GitHub Enterprise CloudまたはGitHub.comのライセンスに基づく規約が適用されます。 「個人データ」の利用には、「[GitHubのプライバシーについての声明](/github/site-policy/github-privacy-statement)」が適用されます。
+With GitHub Connect, you can share certain features and data between your GitHub Enterprise Server or GitHub AE instance and your GitHub Enterprise Cloud organization or enterprise account on GitHub.com. In order to enable GitHub Connect, you must have at least one (1) account on GitHub Enterprise Cloud or GitHub.com, and one (1) licensed instance of GitHub Enterprise Server or GitHub AE. Connect経由でのGitHub Enterprise CloudまたはGitHub.comの利用は、GitHub Enterprise CloudまたはGitHub.comのライセンスに基づく規約が適用されます。 「個人データ」の利用には、「[GitHubのプライバシーについての声明](/github/site-policy/github-privacy-statement)」が適用されます。
 
 ## GitHub Enterprise Importer
 Importer is a framework for exporting data from other sources to be imported to the GitHub platform. Importer is provided “AS-IS”.
diff --git a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index b9d860ff80..b170c3c1ee 100644
--- a/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/ja-JP/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -43,6 +43,9 @@ The maximum file size is:
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
+{%- if svg-support %}
+* SVG (*.svg*)
+{%- endif %}
 * ログファイル (*.log*)
 * Microsoft Word (*.docx*)、Powerpoint (*.pptx*)、および Excel (*.xlsx*) 文書
 * テキストファイル (*.txt*)
diff --git a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
index 34d5814a7b..e4137fb95f 100644
--- a/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/issues/tracking-your-work-with-issues/filtering-and-searching-issues-and-pull-requests.md
@@ -104,7 +104,7 @@ Once you've [applied labels to an issue or pull request](/articles/applying-labe
 - マージの前に[レビューが必要](/github/administering-a-repository/about-protected-branches#require-pull-request-reviews-before-merging)なプルリクエスト
 - レビュー担当者が承認したプルリクエスト
 - レビュー担当者が変更を求めているプルリクエスト
-- Pull requests that you have reviewed{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+- Pull requests that you have reviewed{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %}
 - Pull requests that someone has asked you directly to review{% endif %}
 - [自分、または自分のチームに誰かがレビューを依頼](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review)したプルリクエスト
 
@@ -186,7 +186,7 @@ Issueについては、以下も検索に利用できます。
 - レビュー担当者が承認したプルリクエストのフィルタリング: `state:open type:pr review:approved`
 - レビュー担当者が変更を要求したプルリクエストのフィルタリング: `state:open type:pr review:changes_requested`
 - [レビュー担当者](/articles/about-pull-request-reviews/)によるプルリクエストのフィルタリング: `state:open type:pr reviewed-by:octocat`
-- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+- Filter pull requests by the specific user [requested for review](/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review): `state:open type:pr review-requested:octocat`{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %}
 - Filter pull requests that someone has asked you directly to review: `state:open type:pr user-review-requested:@me`{% endif %}
 - レビューを要求されたチームによるプルリクエストのフィルタリング: `state:open type:pr team-review-requested:github/atom`{% ifversion fpt or ghes or ghae or ghec %}
 - プルリクエストでクローズできるIssueにリンクされているプルリクエストのフィルタリング: `linked:issue`{% endif %}
diff --git a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
index ffba21a3d1..a30b8d437d 100644
--- a/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
+++ b/translations/ja-JP/content/pages/setting-up-a-github-pages-site-with-jekyll/creating-a-github-pages-site-with-jekyll.md
@@ -68,7 +68,9 @@ Jekyll を使用して {% data variables.product.prodname_pages %} サイトを
  サイトを `gh-pages` ブランチから公開する場合には、`gh-pages` ブランチを作成してチェックアウトします。
  ```shell
  $ git checkout --orphan gh-pages
- # Creates a new branch, with no history or contents, called gh-pages and switches to the gh-pages branch
+ # Creates a new branch, with no history or contents, called gh-pages, and switches to the gh-pages branch
+ $ git rm -rf 
+ # Removes the contents from your default branch from the working directory
  ```
 1. 新しい Jekyll サイトを作成するには、`jekyll new` コマンドを使用します。
    ```shell
diff --git a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
index 315b1d3d70..b38d054831 100644
--- a/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
+++ b/translations/ja-JP/content/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/using-a-merge-queue.md
@@ -17,7 +17,7 @@ shortTitle: Use merge queue
 
 {% data reusables.pull_requests.merge-queue-overview %}
 
-The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh/readonly/queue/{base_branch}`.
+The merge queue creates temporary preparatory branches to validate pull requests against the latest version of the base branch. To ensure that {% data variables.product.prodname_dotcom %} validates these preparatory branches, you may need to update your CI configuration to trigger builds on branch names starting with `gh-readonly-queue/{base_branch}`.
 
 For example, with {% data variables.product.prodname_actions %}, adding the following trigger to a workflow will cause the workflow to run when any push is made to a merge queue preparatory branch that targets `main`.
 
@@ -25,7 +25,8 @@ For example, with {% data variables.product.prodname_actions %}, adding the foll
 on:
   push:
     branches:
-    - gh/readonly/queue/main/**
+    - main
+    - gh-readonly-queue/main/**
 ```
 
 {% data reusables.pull_requests.merge-queue-merging-method %}
diff --git a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
index f3308a7872..37f6dba576 100644
--- a/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
+++ b/translations/ja-JP/content/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository.md
@@ -45,7 +45,10 @@ shortTitle: Manage GitHub Actions settings
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions %}
-1. [**Actions permissions**] で、オプションを選択します。 ![この Organization に対するアクションポリシーを設定する](/assets/images/help/repository/actions-policy.png)
+1. [**Actions permissions**] で、オプションを選択します。
+
+  ![この Organization に対するアクションポリシーを設定する](/assets/images/help/repository/actions-policy.png)
+
 1. [**Save**] をクリックします。
 
 ## 特定のアクションの実行を許可する
@@ -56,12 +59,14 @@ shortTitle: Manage GitHub Actions settings
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions %}
 1. [**Actions permissions**] で [**Allow select actions**] を選択し、必要なアクションをリストに追加します。
+
    {%- ifversion ghes > 3.0 %}
    ![許可リストにアクションを追加する](/assets/images/help/repository/actions-policy-allow-list.png)
    {%- else %}
    ![許可リストにアクションを追加する](/assets/images/enterprise/github-ae/repository/actions-policy-allow-list.png)
    {%- endif %}
-2. [**Save**] をクリックします。
+
+1. [**Save**] をクリックします。
 
 {% ifversion fpt or ghec %}
 ## パブリックフォークからのワークフローに対する必須の承認の設定
@@ -103,7 +108,10 @@ The default permissions can also be configured in the organization settings. If
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.settings-sidebar-actions %}
-1. [**Workflow permissions**]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。 ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+1. [**Workflow permissions**]の下で、`GITHUB_TOKEN`にすべてのスコープに対する読み書きアクセスを持たせたいか、あるいは`contents`スコープに対する読み取りアクセスだけを持たせたいかを選択してください。
+
+  ![Set GITHUB_TOKEN permissions for this repository](/assets/images/help/settings/actions-workflow-permissions-repository.png)
+
 1. **Save（保存）**をクリックして、設定を適用してください。
 {% endif %}
 
@@ -112,15 +120,18 @@ The default permissions can also be configured in the organization settings. If
 
 Members of your enterprise can use internal repositories to work on projects without sharing information publicly. For information, see "[About repositories](/repositories/creating-and-managing-repositories/about-repositories#about-internal-repositories)."
 
-To configure whether workflows in an internal repository can be accessed from outside the repository:
+You can configure whether {% if internal-actions%}actions and {% endif %}workflows in an internal repository can be accessed from outside the repository.{% if internal-actions %} For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."{% endif %}
 
 1. On {% data variables.product.prodname_dotcom %}, navigate to the main page of the internal repository.
 1. Under your repository name, click {% octicon "gear" aria-label="The gear icon" %} **Settings**.
 {% data reusables.repositories.settings-sidebar-actions %}
-1. Under **Access**, choose one of the access settings: ![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png)
-   * **Not accessible** - Workflows in other repositories can't use workflows in this repository.
-   * **Accessible from repositories in the '&lt;organization name&gt;' organization** - Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.
-   * **Accessible from repositories in the '&lt;enterprise name&gt;' enterprise** - Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.
+1. Under **Access**, choose one of the access settings:
+
+   {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}![Set the access to Actions components](/assets/images/help/settings/actions-access-settings.png){% else %}![Set the access to Actions components](/assets/images/enterprise/3.4/actions-access-settings.png){% endif %}
+
+   * **Not accessible** - Workflows in other repositories cannot access this repository.
+   * **Accessible from repositories in the 'ORGANIZATION NAME' organization** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ORGANIZATION NAME' organization can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same organization and their visibility is private or internal.{% endif %}
+   * **Accessible from repositories in the 'ENTERPRISE NAME' enterprise** - {% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}Workflows in other repositories that are part of the 'ENTERPRISE NAME' enterprise can access the actions and workflows in this repository. Access is allowed only from private or internal repositories.{% else %}Workflows in other repositories can use workflows in this repository if they are part of the same enterprise and their visibility is private or internal.{% endif %}
 1. **Save（保存）**をクリックして、設定を適用してください。
 {% endif %}
 
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
index ee3583001d..9368e32a57 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/about-searching-on-github.md
@@ -70,8 +70,8 @@ If you use {% ifversion fpt or ghec %}{% data variables.product.prodname_ghe_ser
 
 {% ifversion fpt or ghes or ghec %}
 
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
-- "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)" in the {% data variables.product.prodname_ghe_managed %} documentation
+- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise]({% ifversion not ghes %}/enterprise-server@latest{% endif %}/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}
+- "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)" in the {% data variables.product.prodname_ghe_managed %} documentation
 
 {% ifversion ghes or ghae %}
 
diff --git a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
index 3bcb810dbf..1be94c97f0 100644
--- a/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
+++ b/translations/ja-JP/content/search-github/getting-started-with-searching-on-github/enabling-githubcom-repository-search-from-your-private-enterprise-environment.md
@@ -25,8 +25,8 @@ You can search for designated private repositories on {% data variables.product.
 ## 必要な環境
 
 - An enterprise owner for {% ifversion fpt or ghec %}your private {% data variables.product.prodname_enterprise %} environment{% else %}{% data variables.product.product_name %}{% endif %} must enable {% data variables.product.prodname_github_connect %} and {% data variables.product.prodname_unified_search %} for private repositories. For more information, see the following.{% ifversion fpt or ghes or ghec %}
-  - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/{% ifversion ghes %}{{ currentVersion }}{% else %}enterprise-server@latest{% endif %}/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
-  - "[Enabling {% data variables.product.prodname_unified_search %} between your enterprise account and {% data variables.product.prodname_dotcom_the_website %}](/github-ae@latest/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
+  - "\[Enabling {% data variables.product.prodname_unified_search %} for your enterprise\](/{% ifversion not ghes %}enterprise-server@latest/{% endif %}admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_server %} documentation{% endif %}{% endif %}{% ifversion fpt or ghec or ghae %}
+  - "[Enabling {% data variables.product.prodname_unified_search %} for your enterprise}](/github-ae@latest/admin/configuration/configuring-github-connect/enabling-unified-search-for-your-enterprise)"{% ifversion fpt or ghec %} in the {% data variables.product.prodname_ghe_managed %} documentation{% endif %}
 {% endif %}
 
 - You must already have access to the private repositories and connect your account {% ifversion fpt or ghec %}in your private {% data variables.product.prodname_enterprise %} environment{% else %}on {% data variables.product.product_name %}{% endif %} with your account on {% data variables.product.prodname_dotcom_the_website %}. For more information about the repositories you can search, see "[About searching on GitHub](/github/searching-for-information-on-github/getting-started-with-searching-on-github/about-searching-on-github#searching-repositories-on-githubcom-from-your-private-enterprise-environment)."
diff --git a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
index ee4d9e59e7..0c18bc6444 100644
--- a/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
+++ b/translations/ja-JP/content/search-github/searching-on-github/searching-issues-and-pull-requests.md
@@ -246,16 +246,16 @@ shortTitle: Search issues & PRs
 
 レビュー担当者およびレビューリクエストを受けた人で、[レビューステータス](/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/about-pull-request-reviews) (_none_、_required_、_approved_、または _changes requested_) でプルリクエストをフィルタリングできます。
 
-| 修飾子                        | サンプル                                                                                                                                                                                                                                                                                                                                                                                                                          |
-| -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `review:none`              | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) は、レビューされていないプルリクエストにマッチします。                                                                                                                                                                                                                                                                                         |
-| `review:required`          | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) は、マージ前にレビューが必要なプルリクエストにマッチします。                                                                                                                                                                                                                                                                              |
-| `review:approved`          | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) は、レビュー担当者が承認したプルリクエストにマッチします。                                                                                                                                                                                                                                                                               |
-| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) は、レビュー担当者が変更を求めたプルリクエストにマッチします。                                                                                                                                                                                                                                                           |
-| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) は、特定の人がレビューしたプルリクエストにマッチします。                                                                                                                                                                                                                                                                  |
-| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) は、特定の人にレビューがリクエストされているプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae or ghes > 3.2 or ghec %}
+| 修飾子                        | サンプル                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| -------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `review:none`              | [**type:pr review:none**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Anone&type=Issues) は、レビューされていないプルリクエストにマッチします。                                                                                                                                                                                                                                                                                                    |
+| `review:required`          | [**type:pr review:required**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Arequired&type=Issues) は、マージ前にレビューが必要なプルリクエストにマッチします。                                                                                                                                                                                                                                                                                         |
+| `review:approved`          | [**type:pr review:approved**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Aapproved&type=Issues) は、レビュー担当者が承認したプルリクエストにマッチします。                                                                                                                                                                                                                                                                                          |
+| `review:changes_requested` | [**type:pr review:changes_requested**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review%3Achanges_requested&type=Issues) は、レビュー担当者が変更を求めたプルリクエストにマッチします。                                                                                                                                                                                                                                                                      |
+| <code>reviewed-by:<em>USERNAME</em></code> | [**type:pr reviewed-by:gjtorikian**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+reviewed-by%3Agjtorikian&type=Issues) は、特定の人がレビューしたプルリクエストにマッチします。                                                                                                                                                                                                                                                                             |
+| <code>review-requested:<em>USERNAME</em></code> | [**type:pr review-requested:benbalter**](https://github.com/search?utf8=%E2%9C%93&q=type%3Apr+review-requested%3Abenbalter&type=Issues) は、特定の人にレビューがリクエストされているプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。 If the requested person is on a team that is requested for review, then review requests for that team will also appear in the search results.{% ifversion fpt or ghae-issue-5181 or ghes > 3.2 or ghec %}
 | <code>user-review-requested:@me</code> | [**type:pr user-review-requested:@me**](https://github.com/search?q=is%3Apr+user-review-requested%3A%40me+) matches pull requests that you have directly been asked to review.{% endif %}
-| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) は、Team `atom/design`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。                                                                                                                                                                                  |
+| <code>team-review-requested:<em>TEAMNAME</em></code> | [**type:pr team-review-requested:atom/design**](https://github.com/search?q=type%3Apr+team-review-requested%3Aatom%2Fdesign&type=Issues) は、Team `atom/design`からのレビューリクエストがあるプルリクエストにマッチします。 リクエストを受けたレビュー担当者は、プルリクエストのレビュー後は検索結果に表示されなくなります。                                                                                                                                                                                             |
 
 ## Issue やプルリクエストの作成時期や最終更新時期で検索
 
diff --git a/translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml b/translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml
index 1b0a06a45f..454d145e07 100644
--- a/translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml
+++ b/translations/ja-JP/data/features/enterprise-owners-visible-for-org-members.yml
@@ -3,5 +3,5 @@
 #Documentation for enterprise owners UI updates
 versions:
   ghes: '>=3.4'
-  ghae: 'issue-####'
+  ghae: 'issue-5741'
   ghec: '*'
diff --git a/translations/ja-JP/data/features/internal-actions.yml b/translations/ja-JP/data/features/internal-actions.yml
new file mode 100644
index 0000000000..1be6a278de
--- /dev/null
+++ b/translations/ja-JP/data/features/internal-actions.yml
@@ -0,0 +1,5 @@
+---
+versions:
+  ghec: '*'
+  ghes: '>=3.5'
+  ghae: 'issue-5610'
diff --git a/translations/ja-JP/data/features/svg-support.yml b/translations/ja-JP/data/features/svg-support.yml
new file mode 100644
index 0000000000..6636cc97e6
--- /dev/null
+++ b/translations/ja-JP/data/features/svg-support.yml
@@ -0,0 +1,6 @@
+---
+#Releases issue #1951
+#Support upload of SVG files
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/ja-JP/data/reusables/actions/internal-actions-summary.md b/translations/ja-JP/data/reusables/actions/internal-actions-summary.md
new file mode 100644
index 0000000000..3efefb4211
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/internal-actions-summary.md
@@ -0,0 +1,3 @@
+{% if internal-actions %}
+To share actions across your enterprise without publishing the actions publicly, you can store the actions in an internal repository, then configure the repository to allow access to {% data variables.product.prodname_actions %} workflows in other repositories owned by the same organization or by any organization in the enterprise. For more information, see "[Sharing actions and workflows with your enterprise](/actions/creating-actions/sharing-actions-and-workflows-with-your-enterprise)."
+{% endif %}
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/outside-collaborators-internal-actions.md b/translations/ja-JP/data/reusables/actions/outside-collaborators-internal-actions.md
new file mode 100644
index 0000000000..fcf164b2d1
--- /dev/null
+++ b/translations/ja-JP/data/reusables/actions/outside-collaborators-internal-actions.md
@@ -0,0 +1 @@
+If you make an internal repository in your enterprise accessible to {% data variables.product.prodname_actions %} workflows in other repositories, outside collaborators on the other repositories can indirectly access the internal repository, even though they do not have direct access to the internal repository. The outside collaborators can view logs for workflow runs when actions or workflows from the internal repository are used.
\ No newline at end of file
diff --git a/translations/ja-JP/data/reusables/actions/reusable-workflows.md b/translations/ja-JP/data/reusables/actions/reusable-workflows.md
index 60451866a4..81a4a7dfea 100644
--- a/translations/ja-JP/data/reusables/actions/reusable-workflows.md
+++ b/translations/ja-JP/data/reusables/actions/reusable-workflows.md
@@ -1,5 +1,4 @@
 {% ifversion fpt or ghes > 3.3 or ghae-issue-4757 or ghec %}
-## Reusing workflows
 
-You can call one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
+{% ifversion ghes or ghec or ghae %}You can share workflows with your organization, publicly or privately, by calling{% else %} You can call{% endif %} one workflow from within another workflow. This allows you to reuse workflows, avoiding duplication and making your workflows easier to maintain. For more information, see "[Reusing workflows](/actions/learn-github-actions/reusing-workflows)."
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md b/translations/ja-JP/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
index 8d814ccdb2..d2284b0bec 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-run-on-specific-branches-or-tags.md
@@ -7,7 +7,7 @@ Use the `tags` filter when you want to include tag name patterns or when you wan
 
 If you define only `tags`/`tag-ignore` or only `branches`/`branches-ignore`, the workflow won't run for events affecting the undefined Git ref. If you define neither  `tags`/`tag-ignore` or `branches`/`branches-ignore`, the workflow will run for events affecting either branches or tags. If you define both `branches`/`branches-ignore` and [`paths`](#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
 
-The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+The `branches`, `branches-ignore`, `tags`, and `tags-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch or tag name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
 #### Example: Including branches and tags
 
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-specifying-branches.md b/translations/ja-JP/data/reusables/actions/workflows/section-specifying-branches.md
index 0ca962cdf7..81ac96eed2 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-specifying-branches.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-specifying-branches.md
@@ -1,7 +1,7 @@
 
 When using the `workflow_run` event, you can specify what branches the triggering workflow must run on in order to trigger your workflow.
 
-The `branches` and `branches-ignore` filters accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+The `branches` and `branches-ignore` filters accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to *escape* each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
 For example, a workflow with the following trigger will only run when the workflow named `Build` runs on a branch whose name starts with `releases/`:
 
@@ -42,4 +42,4 @@ on:
     branches:
       - 'releases/**'
       - '!releases/**-alpha'
-```
\ No newline at end of file
+```
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
index 57e2c9e910..c26c789f39 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-branches.md
@@ -4,7 +4,7 @@ Use the `branches` filter when you want to include branch name patterns or when
 
 If you define both `branches`/`branches-ignore` and [`paths`](#onpushpull_requestpull_request_targetpathspaths-ignore), the workflow will only run when both filters are satisfied.
 
-The `branches` and `branches-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to escape each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](#filter-pattern-cheat-sheet)."
+The `branches` and `branches-ignore` keywords accept glob patterns that use characters like `*`, `**`, `+`, `?`, `!` and others to match more than one branch name. If a name contains any of these characters and you want a literal match, you need to escape each of these special characters with `\`. For more information about glob patterns, see the "[Filter pattern cheat sheet](/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
 #### Example: Including branches
 
diff --git a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
index 7eb1d7eab2..6ad78da438 100644
--- a/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
+++ b/translations/ja-JP/data/reusables/actions/workflows/section-triggering-a-workflow-paths.md
@@ -5,7 +5,7 @@ Use the `paths` filter when you want to include file path patterns or when you w
 
 If you define both `branches`/`branches-ignore` and `paths`, the workflow will only run when both filters are satisfied.
 
-The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. 詳しい情報については、「[フィルタパターンのチートシート](#filter-pattern-cheat-sheet)」を参照してください。
+The `paths` and `paths-ignore` keywords accept glob patterns that use the `*` and `**` wildcard characters to match more than one path name. For more information, see the "[Filter pattern cheat sheet]/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet)."
 
 #### Example: Including paths
 
diff --git a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
index eb537bfd85..8d32bf7827 100644
--- a/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
+++ b/translations/ja-JP/data/reusables/dependabot/dependabot-alerts-dependency-graph-enterprise.md
@@ -1,3 +1,3 @@
 {% ifversion ghes or ghae-issue-4864 %}
-The dependency graph and {% data variables.product.prodname_dependabot_alerts %} are configured at an enterprise level by the enterprise owner. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+The dependency graph and {% data variables.product.prodname_dependabot_alerts %} are configured at an enterprise level by the enterprise owner. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 {% endif %} 
diff --git a/translations/ja-JP/data/reusables/enterprise/link-to-ghec-trial.md b/translations/ja-JP/data/reusables/enterprise/link-to-ghec-trial.md
index 31c4e5a5a8..62aef21ed5 100644
--- a/translations/ja-JP/data/reusables/enterprise/link-to-ghec-trial.md
+++ b/translations/ja-JP/data/reusables/enterprise/link-to-ghec-trial.md
@@ -1 +1 @@
-For more information about how you can try {% data variables.product.prodname_ghe_cloud %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}](/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)."
+For more information about how you can try {% data variables.product.prodname_ghe_cloud %} for free, see "[Setting up a trial of {% data variables.product.prodname_ghe_cloud %}]({% ifversion ghae %}/enterprise-cloud@latest{% endif %}/get-started/signing-up-for-github/setting-up-a-trial-of-github-enterprise-cloud)."
diff --git a/translations/ja-JP/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md b/translations/ja-JP/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
index 37b1ab5120..2d14b4409d 100644
--- a/translations/ja-JP/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
+++ b/translations/ja-JP/data/reusables/enterprise/verify-audit-log-streaming-endpoint.md
@@ -1 +1 @@
-1. Verify the endpoint, then click **Save**.
+1. After you have successfully verified the endpoint, click **Save**.
diff --git a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md
index 7775e50f47..28d7ac275f 100644
--- a/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md
+++ b/translations/ja-JP/data/reusables/repositories/enable-security-alerts.md
@@ -1,4 +1,4 @@
 {% ifversion ghes or ghae-issue-4864 %}
 Enterprise owners must enable
-{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} on your enterprise account](/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-the-dependency-graph-and-dependabot-alerts-on-your-enterprise-account)."
+{% data variables.product.prodname_dependabot_alerts %} for vulnerable dependencies for {% data variables.product.product_location %} before you can use this feature. For more information, see "[Enabling the dependency graph and {% data variables.product.prodname_dependabot_alerts %} for your enterprise](/admin/configuration/configuring-github-connect/enabling-the-dependency-graph-and-dependabot-alerts-for-your-enterprise)."
 {% endif %}
diff --git a/translations/ja-JP/data/reusables/repositories/settings-sidebar-actions.md b/translations/ja-JP/data/reusables/repositories/settings-sidebar-actions.md
index 0d20efc2bd..c350461a12 100644
--- a/translations/ja-JP/data/reusables/repositories/settings-sidebar-actions.md
+++ b/translations/ja-JP/data/reusables/repositories/settings-sidebar-actions.md
@@ -1 +1,5 @@
-1. サイドバーで**Actions（アクション）**をクリックしてください。
+1. In the left sidebar, click **Actions**{% ifversion ghes > 3.4 or ghae-issue-6090 or ghec %}, then **General**.
+
+   ![The Actions > General sidebar option](/assets/images/help/repository/actions-general-tab.png)
+
+{% else %}.{% endif %}
diff --git a/translations/log/ja-resets.csv b/translations/log/ja-resets.csv
index ed774e379a..92c0271871 100644
--- a/translations/log/ja-resets.csv
+++ b/translations/log/ja-resets.csv
@@ -31,10 +31,6 @@ translations/ja-JP/content/admin/configuration/configuring-your-enterprise/confi
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/initializing-github-ae.md,broken liquid tags
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/managing-github-mobile-for-your-enterprise.md,broken liquid tags
 translations/ja-JP/content/admin/configuration/configuring-your-enterprise/site-admin-dashboard.md,broken liquid tags
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/connecting-your-enterprise-account-to-github-enterprise-cloud.md,broken liquid tags
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-contributions-between-your-enterprise-account-and-githubcom.md,broken liquid tags
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/enabling-unified-search-between-your-enterprise-account-and-githubcom.md,broken liquid tags
-translations/ja-JP/content/admin/configuration/managing-connections-between-your-enterprise-accounts/index.md,broken liquid tags
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md,Listed in localization-support#489
 translations/ja-JP/content/admin/enterprise-management/configuring-clustering/monitoring-cluster-nodes.md,parsing error
 translations/ja-JP/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/increasing-cpu-or-memory-resources.md,broken liquid tags
diff --git a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index 1180eb3bdb..db21e5b40d 100644
--- a/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/pt-BR/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -43,6 +43,9 @@ Arquivos compatíveis:
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
+{%- if svg-support %}
+* SVG (*.svg*)
+{%- endif %}
 * Arquivos log (*.log*)
 * Documentos do Microsoft Word (*.docx*), Powerpoint (*.pptx*), e Excel (*.xlsx*)
 * Arquivos de texto (*.txt*)
diff --git a/translations/pt-BR/data/features/svg-support.yml b/translations/pt-BR/data/features/svg-support.yml
new file mode 100644
index 0000000000..6636cc97e6
--- /dev/null
+++ b/translations/pt-BR/data/features/svg-support.yml
@@ -0,0 +1,6 @@
+---
+#Releases issue #1951
+#Support upload of SVG files
+versions:
+  fpt: '*'
+  ghec: '*'
diff --git a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
index c47c20d0c5..07cce93eea 100644
--- a/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
+++ b/translations/zh-CN/content/github/writing-on-github/working-with-advanced-formatting/attaching-files.md
@@ -43,6 +43,9 @@ topics:
 * PNG (*.png*)
 * GIF (*.gif*)
 * JPEG (*.jpg*)
+{%- if svg-support %}
+* SVG (*.svg*)
+{%- endif %}
 * 日志文件 (*.log*)
 * Microsoft Word (*.docx*)、Powerpoint (*.pptx*) 和 Excel (*.xlsx*) 文档
 * 文本文件 (*.txt*)
diff --git a/translations/zh-CN/data/features/svg-support.yml b/translations/zh-CN/data/features/svg-support.yml
new file mode 100644
index 0000000000..6636cc97e6
--- /dev/null
+++ b/translations/zh-CN/data/features/svg-support.yml
@@ -0,0 +1,6 @@
+---
+#Releases issue #1951
+#Support upload of SVG files
+versions:
+  fpt: '*'
+  ghec: '*'