Repo sync

content/actions/learn-github-actions/variables.md

@@ -111,7 +111,7 @@ The following rules apply to configuration variable names:
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.actions.sidebar-secrets-and-variables %}
 {% data reusables.actions.actions-variables-tab %}
-   ![Screenshot of the "Actions secrets and variables" page. The "Variables" tab is highlighted with a dark orange outline.](/assets/images/help/repository/actions-variables-tab.png)
+   ![Screenshot of the "Actions secrets and variables" page. The "Variables" tab is outlined in dark orange.](/assets/images/help/repository/actions-variables-tab.png)
 1. Click **New repository variable**.
 {% data reusables.actions.variable-fields %}
 1. Click **Add variable**.
@@ -139,10 +139,9 @@ The following rules apply to configuration variable names:
 {% data reusables.actions.sidebar-secrets-and-variables %}
 {% data reusables.actions.actions-variables-tab %}
 
-   ![Screenshot of the "Actions secrets and variables" page. A tab, labeled "Variables," is outlined in dark orange.](/assets/images/help/actions/organization-variables-tab.png)
+   ![Screenshot of the "Actions secrets and variables" page. The "Variables" tab is outlined in dark orange.](/assets/images/help/repository/actions-variables-tab.png)
 
    {% data reusables.actions.secrets-and-variables-org-permissions %}
-
 1. Click **New organization variable**.
 {% data reusables.actions.variable-fields %}
 1. From the **Repository access** dropdown list, choose an access policy.

content/actions/security-guides/using-secrets-in-github-actions.md

@@ -80,7 +80,7 @@ Instead of using a {% data variables.product.pat_generic %}, consider using a {%
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.actions.sidebar-secrets-and-variables %}
 {% data reusables.actions.actions-secrets-tab %}
-   ![Screenshot of the "Actions secrets and variables" page.](/assets/images/help/repository/actions-secrets-tab.png)
+   ![Screenshot of the "Actions secrets and variables" page. The "Secrets" tab is outlined in dark orange.](/assets/images/help/repository/actions-secrets-tab.png)
 1. Click **New repository secret**.
 1. In the **Name** field, type a name for your secret.
 1. In the **Secret** field, enter the value for your secret.
@@ -156,7 +156,7 @@ gh secret list --env ENV_NAME
 {% data reusables.actions.sidebar-secrets-and-variables %}
 {% data reusables.actions.actions-secrets-tab %}
 
-   ![Screenshot of the "Actions secrets and variables" page. A tab, labeled "Secrets," is outlined in dark orange.](/assets/images/help/actions/organization-secrets-tab.png)
+   ![Screenshot of the "Actions secrets and variables" page. The "Secrets" tab is outlined in dark orange.](/assets/images/help/repository/actions-secrets-tab.png)
 
    {% data reusables.actions.secrets-and-variables-org-permissions %}
 

content/codespaces/managing-codespaces-for-your-organization/managing-development-environment-secrets-for-your-repository-or-organization.md

@@ -80,11 +80,7 @@ You can check which access policies are applied to a development environment sec
 {% data reusables.organizations.org_settings %}
 {% data reusables.codespaces.sidebar-secret %}
 
-1. The list of secrets includes any configured permissions and policies. For example:
-
-   ![Screenshot showing a list of two secrets. To the right of each is an edit button and a delete button.](/assets/images/help/codespaces/org-secrets-list.png)
-
-1. For more details on the configured permissions for each secret, click **Update**.
+1. Optionally, to view or edit the configured permissions for each secret, to the right of the secret, click {% octicon "pencil" aria-label="Edit secret" %}.
 
 ## Further reading