repo sync

content/actions/monitoring-and-troubleshooting-workflows/using-workflow-run-logs.md

@@ -63,7 +63,6 @@ You can download the log files from your workflow run. You can also download a w
 
   ![Screenshot of the log for a job. In the header, a gear icon is outlined in dark orange.](/assets/images/help/actions/download-logs-drop-down.png)
 
-
   {% ifversion re-run-jobs %}
 
   {% note %}
@@ -82,11 +81,11 @@ You can delete the log files from your workflow run. {% data reusables.repositor
 {% data reusables.repositories.actions-tab %}
 {% data reusables.repositories.navigate-to-workflow %}
 {% data reusables.repositories.view-run %}
-1. In the upper right corner, click {% octicon "kebab-horizontal" aria-label="Show options" %}.
+1. In the upper-right corner, select the {% octicon "kebab-horizontal" aria-label="Show workflow options" %} dropdown menu, then click **Delete all logs**.
 
-    ![Kebab-horizontal icon](/assets/images/help/repository/workflow-run-kebab-horizontal-icon-updated-2.png)
+    ![Screenshot of the page for a workflow run. In the top-right corner, a button, labeled with a kebab icon, is outlined in dark orange.](/assets/images/help/actions/workflow-run-kebab-horizontal-icon.png)
 
-2. To delete the log files, click the **Delete all logs** button and review the confirmation prompt.
+1. Review the confirmation prompt.
 
 After deleting logs, the **Delete all logs** button is removed to indicate that no log files remain in the workflow run.
 

content/code-security/secret-scanning/configuring-secret-scanning-for-your-repositories.md

@@ -46,14 +46,12 @@ You can enable {% data variables.secret-scanning.user_alerts %} for any {% ifver
 {% data reusables.repositories.sidebar-settings %}
 {% data reusables.repositories.navigate-to-code-security-and-analysis %}{% ifversion ghec or ghes or ghae %}
 1. If {% data variables.product.prodname_advanced_security %} is not already enabled for the repository, to the right of "{% data variables.product.prodname_GH_advanced_security %}", click **Enable**.
-   {% ifversion ghec %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/help/repository/enable-ghas-dotcom.png)
-   {% elsif ghes or ghae %}![Enable {% data variables.product.prodname_GH_advanced_security %} for your repository](/assets/images/enterprise/3.1/help/repository/enable-ghas.png){% endif %}
 1. Review the impact of enabling {% data variables.product.prodname_advanced_security %}, then click **Enable {% data variables.product.prodname_GH_advanced_security %} for this repository**.
-1. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled. 
-   
+1. When you enable {% data variables.product.prodname_advanced_security %}, {% data variables.product.prodname_secret_scanning %} may automatically be enabled for the repository due to the organization's settings. If "{% data variables.product.prodname_secret_scanning_caps %}" is shown with an **Enable** button, you still need to enable {% data variables.product.prodname_secret_scanning %} by clicking **Enable**. If you see a **Disable** button, {% data variables.product.prodname_secret_scanning %} is already enabled.
+
    ![Screenshot of the "{% data variables.product.prodname_secret_scanning_caps %}" section of the "Code security and analysis" page, with the "Enable" button highlighted in a dark orange outline.](/assets/images/help/repository/enable-secret-scanning-alerts.png){% endif %}{% ifversion fpt %}
-1. Scroll down to the bottom of the page, and click **Enable** for {% data variables.product.prodname_secret_scanning %}. If you see a **Disable** button, it means that {% data variables.product.prodname_secret_scanning %} is already enabled for the repository. 
-   
+1. Scroll down to the bottom of the page, and click **Enable** for {% data variables.product.prodname_secret_scanning %}. If you see a **Disable** button, it means that {% data variables.product.prodname_secret_scanning %} is already enabled for the repository.
+
    ![Screenshot of the "{% data variables.product.prodname_secret_scanning_caps %}" section of the "Code security and analysis" page, with the "Enable" button highlighted in a dark orange outline.](/assets/images/help/repository/enable-secret-scanning-alerts.png){% endif %}
 
 {% ifversion secret-scanning-push-protection %}

content/communities/setting-up-your-project-for-healthy-contributions/creating-a-default-community-health-file.md

@@ -46,12 +46,12 @@ 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 ghes or ghec %} or personal account{% endif %} you want to create default files for.
+1. Use the **Owner** drop-down menu, and select the organization{% ifversion fpt or ghes or ghec %} or personal 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)
-4. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
+1. In the "Repository name" field, type **.github**.
+1. Optionally, in the "Description" field, type a description.
+1. Make sure the repository status is set to **Public** (a repository for default files cannot be private).
   ![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 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 "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."
+1. 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 "[AUTOTITLE](/repositories/working-with-files/managing-files/creating-new-files)."

content/get-started/privacy-on-github/opting-into-or-out-of-the-github-archive-program-for-your-public-repository.md

@@ -19,8 +19,7 @@ If you opt out of the {% data variables.product.prodname_archive %} for a reposi
 
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.sidebar-settings %}
-3. Under "Features", select or unselect **Preserve this repository**.
-    ![Checkbox for allowing {% data variables.product.prodname_dotcom %} to include your code in the {% data variables.product.prodname_archive %}](/assets/images/help/repository/github-archive-program-checkbox.png)
+1. Under "Features", select or deselect **Preserve this repository**.
 
 ## Further reading
 - [{% data variables.product.prodname_archive %} FAQ](https://archiveprogram.github.com/faq/)

content/get-started/privacy-on-github/requesting-an-archive-of-your-personal-accounts-data.md

@@ -30,17 +30,15 @@ The generated `tar.gz` file reflects the data stored at the time you started the
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.account_settings %}
-3. Under "Export account data", click **Start export** or **New export**.
-![Start personal data export button highlighted](/assets/images/help/repository/export-personal-data.png)
-![New personal data export button highlighted](/assets/images/help/repository/new-export.png)
-4. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address.
-5. Click the download link in your email and re-enter your password if prompted.
-6. You'll be redirected to a `tar.gz` file that you can download.
+1. Under "Export account data", click **Start export** or **New export**.
+1. Once the export is ready to download, {% data variables.product.product_name %} will send you a download link to your primary email address.
+1. Click the download link in your email and re-enter your password if prompted.
+1. You'll be redirected to a `tar.gz` file that you can download.
 
 ## Deleting access to an archive of your personal account's data
 
 You can disable the download link sent to your email before an export expires by deleting the export.
 
 {% data reusables.user-settings.access_settings %}
 {% data reusables.user-settings.account_settings %}
-3. In the "Export account data" section, next to the data export download you want to disable, click **Delete**.
+1. In the "Export account data" section, next to the data export download you want to disable, click **Delete**.

content/get-started/quickstart/contributing-to-projects.md

@@ -16,7 +16,7 @@ topics:
 
 ## About forking
 
-If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow. 
+If you want to contribute to someone else's project but don't have write access to the repository, you can use a "fork and pull request" workflow.
 
 {% data reusables.repositories.fork-definition-long %}
 
@@ -27,18 +27,17 @@ You can contribute by submitting pull requests from your fork to the upstream re
 This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Knife), a test repository that's hosted on {% data variables.product.prodname_dotcom_the_website %} that lets you test the fork and pull request workflow.
 
 1. Navigate to the `Spoon-Knife` project at https://github.com/octocat/Spoon-Knife.
-2. Click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
-3. Select an owner for the forked repository.
-   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further. 
-   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
-5. Optionally, add a description of your fork.
-   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
-6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
-   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
-7. Click **Create fork**.
-   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+1. Click **Fork**.
+
+   ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
+1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
+1. Optionally, in the "Description" field, type a description of your fork.
+1. Optionally, select **Copy the DEFAULT branch only**.
+
+    For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.
+1. Click **Create fork**.
 
 {% note %}
 

content/get-started/quickstart/fork-a-repo.md

@@ -56,20 +56,19 @@ If you haven't yet, first set up Git and authentication with {% data variables.l
 You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked.
 
 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom_the_website %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository.
-2. In the top-right corner of the page, click **Fork**.
-   ![Fork button](/assets/images/help/repository/fork_button.png){% ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
-3. Select an owner for the forked repository.
-   ![Create a new fork page with owner dropdown emphasized](/assets/images/help/repository/fork-choose-owner.png)
-4. By default, forks are named the same as their upstream repositories. You can change the name of the fork to distinguish it further.
-   ![Create a new fork page with repository name field emphasized](/assets/images/help/repository/fork-choose-repo-name.png)
-5. Optionally, add a description of your fork.
-   ![Create a new fork page with description field emphasized](/assets/images/help/repository/fork-description.png)
+1. In the top-right corner of the page, click **Fork**.
+
+   ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork_button.png)
+{%- ifversion fpt or ghec or ghes > 3.5 or ghae > 3.5 %}
+1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
+1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
+1. Optionally, in the "Description" field, type a description of your fork.
 {%- ifversion fpt or ghec or ghes > 3.6 or ghae > 3.6 %}
-6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.
-   ![Option to copy only the default branch](/assets/images/help/repository/copy-default-branch-only.png)
+1. Optionally, select **Copy the DEFAULT branch only**.
+
+   For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork.
 {%- endif %}
-7. Click **Create fork**.
-   ![Emphasized create fork button](/assets/images/help/repository/fork-create-button.png)
+1. Click **Create fork**.
 
 
 {% note %}

content/get-started/quickstart/hello-world.md

@@ -34,13 +34,11 @@ A repository is usually used to organize a single project. Repositories can cont
 Your `hello-world` repository can be a place where you store ideas, resources, or even share and discuss things with others.
 
 {% data reusables.repositories.create_new %}
-1. In the **Repository name** box, enter `hello-world`.
-2. In the **Description** box, write a short description.
-3. Select **Add a README file**.
-4. Select whether your repository will be **Public** or **Private**.
-5. Click **Create repository**.
-
-   ![Create a hello world repository](/assets/images/help/repository/hello-world-repo.png)
+1. In the "Repository name" box, type `hello-world`.
+1. In the "Description" box, type a short description.
+1. Select whether your repository will be **Public** or **Private**.
+1. Select **Add a README file**.
+1. Click **Create repository**.
 
 ## Creating a branch
 
@@ -77,7 +75,7 @@ Here at {% data variables.product.product_name %}, our developers, writers, and
 1. Type a branch name, `readme-edits`, into the text box.
 1. Click **Create branch: readme-edits from main**.
 
-![Branch menu](/assets/images/help/repository/new-branch.png)
+   ![Screenshot of the branch dropdown for a repository. "Create branch: readme-edits from 'main'" is outlined in dark orange.](/assets/images/help/repository/new-branch.png)
 
 Now you have two branches, `main` and `readme-edits`. Right now, they look exactly the same. Next you'll add changes to the new branch.
 
@@ -88,12 +86,10 @@ When you created a new branch in the previous step, {% data variables.product.pr
 You can make and save changes to the files in your repository. On {% data variables.product.product_name %}, saved changes are called commits. Each commit has an associated commit message, which is a description explaining why a particular change was made. Commit messages capture the history of your changes so that other contributors can understand what you’ve done and why.
 
 1. Under the `readme-edits` branch you created, click the _README.md_ file.
-2. Click {% octicon "pencil" aria-label="The edit icon" %} to edit the file.
-3. In the editor, write a bit about yourself. Try using different Markdown elements.
-4. In the **Commit changes** box, write a commit message that describes your changes.
-5. Click **Commit changes**.
-
-   ![Commit example](/assets/images/help/repository/first-commit.png)
+1. To edit the file, click {% octicon "pencil" aria-label="Edit file" %}.
+1. In the editor, write a bit about yourself. Try using different Markdown elements.
+1. In the "Commit changes" box, write a commit message that describes your changes.
+1. Click **Commit changes**.
 
 These changes will be made only to the README file on your `readme-edits` branch, so now this branch contains content that's different from `main`.
 

content/organizations/managing-user-access-to-your-organizations-repositories/viewing-people-with-access-to-your-repository.md

@@ -45,6 +45,5 @@ You can see a combined overview of teams and people with access to your reposito
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.accessing-repository-graphs %}
 {% data reusables.repositories.accessing-repository-people %}
-4. Click **Export CSV**.
-  ![People tab in the repository sidebar](/assets/images/help/repository/export-repository-permissions.png)
+1. Above the list of people, click **Export CSV**.
 {% endif %}

content/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/filtering-files-in-a-pull-request.md

@@ -52,8 +52,7 @@ You can filter files in a pull request by file extension type, such as `.html` o
 
    {% endnote %}
 
-   ![Screenshot of filter changed files search box and file tree emphasized](/assets/images/help/repository/file-tree.png)
-
+   ![Screenshot of the "Files changed" tab of a pull request. In the left sidebar, the file tree is outlined in dark orange.](/assets/images/help/repository/file-tree.png)
 1. To filter by file path, enter part or all of the file path in the **Filter changed files** search box. Alternatively, use the file filter dropdown. For more information, see "[Using the file filter dropdown](#using-the-file-filter-dropdown)."
 
 {% endif %}