Adding fixes for alt image text period (#37646)

Co-authored-by: mc <42146119+mchammer01@users.noreply.github.com>

Author: gracepark

content/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile.md

@@ -21,7 +21,7 @@ You can add personal information about yourself in your bio, like previous place
 
 {% data reusables.profile.profile-readme %}
 
-![Profile README file displayed on profile](/assets/images/help/repository/profile-with-readme.png)
+![Profile README file displayed on profile.](/assets/images/help/repository/profile-with-readme.png)
 
 {% endif %}
 

content/account-and-profile/setting-up-and-managing-your-github-profile/managing-contribution-settings-on-your-profile/sending-enterprise-contributions-to-your-githubcom-profile.md

@@ -45,7 +45,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
 
 1. Sign in to {% data variables.product.prodname_ghe_server %} and {% data variables.product.prodname_dotcom_the_website %}.
 1. On {% data variables.product.prodname_ghe_server %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+   ![Settings icon in the user bar.](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 1. Review the resources that {% data variables.product.prodname_ghe_server %} will access from your {% data variables.product.prodname_dotcom_the_website %} account, then click **Authorize**.
@@ -55,7 +55,7 @@ Before you can connect your {% ifversion fpt or ghec %}{% data variables.product
 
 1. Sign in to {% data variables.product.prodname_ghe_managed %} and {% data variables.product.prodname_dotcom_the_website %}.
 1. On {% data variables.product.prodname_ghe_managed %}, in the upper-right corner of any page, click your profile photo, then click **Settings**.
-   ![Settings icon in the user bar](/assets/images/help/settings/userbar-account-settings.png)
+   ![Settings icon in the user bar.](/assets/images/help/settings/userbar-account-settings.png)
 {% data reusables.github-connect.github-connect-tab-user-settings %}
 {% data reusables.github-connect.connect-dotcom-and-enterprise %}
 {% data reusables.github-connect.authorize-connection %}

content/actions/managing-workflow-runs/reviewing-deployments.md

@@ -42,7 +42,7 @@ If you have configured environment protection rules that control whether softwar
 
 1. Navigate to the workflow run. For more information about navigating to a workflow run, see "[AUTOTITLE](/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history)."
 1. To the right of **Deployment protection rules**, click **Start all waiting jobs**.
-   ![Screenshot of the "Deployment protection rules" section with the "Start all waiting jobs" button outlined in orange](/assets/images/actions-bypass-env-protection-rules.png)
+   ![Screenshot of the "Deployment protection rules" section with the "Start all waiting jobs" button outlined in orange.](/assets/images/actions-bypass-env-protection-rules.png)
 1. In the pop-up window, select the environments for which you want to bypass environment protection rules.
 1. Under **Leave a comment**, enter a description for bypassing the environment protection rules.
 1. Click **I understand the consequences, start deploying**.

content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/configuring-scim-provisioning-for-enterprise-managed-users.md

@@ -50,7 +50,7 @@ To configure provisioning for your {% data variables.enterprise.prodname_emu_ent
 1. Under **Note**, give your token a descriptive name.
 2. Select the **Expiration** dropdown menu, then click **No expiration**.
 3. Select the **admin:enterprise** scope.
-   ![Screenshot showing the admin:enterprise scope](/assets/images/help/enterprises/enterprise-pat-scope.png)
+   ![Screenshot showing the admin:enterprise scope.](/assets/images/help/enterprises/enterprise-pat-scope.png)
 4. Click **Generate token**.
 5. To copy the token to your clipboard, click {% octicon "copy" aria-label="Copy token" %}.
 

content/admin/identity-and-access-management/using-enterprise-managed-users-for-iam/managing-team-memberships-with-identity-provider-groups.md

@@ -75,9 +75,9 @@ Organization owners and team maintainers can manage the existing connection betw
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 1. Optionally, under "Identity Provider Group", to the right of the IdP group you want to disconnect, click {% octicon "x" aria-label="X symbol" %}.
-    ![Unselect a connected IdP group from the GitHub team](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
+    ![Unselect a connected IdP group from the GitHub team.](/assets/images/enterprise/github-ae/teams/unselect-idp-group.png)
 1. To connect an IdP group, under "Identity Provider Group", select the drop-down menu, and click an identity provider group from the list.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+    ![Drop-down menu to choose identity provider group.](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
 1. Click **Save changes**.
 
 ## Viewing IdP groups, group membership, and connected teams

content/admin/identity-and-access-management/using-saml-for-enterprise-iam/mapping-okta-groups-to-teams.md

@@ -58,7 +58,7 @@ You can map a team in your enterprise to an Okta group you previously pushed to
 {% data reusables.organizations.specific_team %}
 {% data reusables.organizations.team_settings %}
 6. Under "Identity Provider Group", select the drop-down menu and click an identity provider group.
-    ![Drop-down menu to choose identity provider group](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
+    ![Drop-down menu to choose identity provider group.](/assets/images/enterprise/github-ae/teams/choose-an-idp-group.png)
 7. Click **Save changes**.
 
 ## Checking the status of your mapped teams

content/admin/user-management/managing-users-in-your-enterprise/viewing-people-in-your-enterprise.md

@@ -160,7 +160,7 @@ You can view a list of all dormant users {% ifversion ghes or ghae %} who have n
 
    ![Screenshot of the tabs above an organization name. The "People" tab is highlighted with an orange outline.](/assets/images/help/enterprises/emu-organization-people-tab.png)
 4. Above the list of members, click **Type**, then select the type of members you want to view.
-   ![Screenshot of the "Type" button](/assets/images/help/enterprises/filter-by-member-type.png)
+   ![Screenshot of the "Type" button.](/assets/images/help/enterprises/filter-by-member-type.png)
 
 {% endif %}
 

content/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account.md

@@ -30,7 +30,7 @@ You can add multiple public keys to your account on {% data variables.product.pr
 {% ifversion upload-expired-or-revoked-gpg-key %}
 To verify as many of your commits as possible, you can add expired and revoked keys. If the key meets all other verification requirements, commits that were previously signed by any of the corresponding private keys will show as verified and indicate that their signing key is expired or revoked.
 
-![A verified commit whose key expired](/assets/images/help/settings/gpg-verified-with-expired-key.png)
+![A verified commit whose key expired.](/assets/images/help/settings/gpg-verified-with-expired-key.png)
 {% endif %}
 
 {% data reusables.gpg.supported-gpg-key-algorithms %}

content/billing/managing-billing-for-github-copilot/viewing-your-github-copilot-usage.md

@@ -36,4 +36,4 @@ The spending information will display the total spending for each organization f
 1. In the "Access" section of the sidebar, click **{% octicon "credit-card" aria-hidden="true" %} Billing and plans**.
 1. Under "{% data variables.product.prodname_copilot_short %}", view the breakdown of your {% data variables.product.prodname_copilot %} usage and upcoming changes in your organization.
 
-   ![Screenshot of the organization-level {% data variables.product.prodname_copilot %} seat usage page](/assets/images/help/copilot/org-level-seat-view.png)
+   ![Screenshot of the organization-level {% data variables.product.prodname_copilot %} seat usage page.](/assets/images/help/copilot/org-level-seat-view.png)

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-for-a-repository.md

@@ -117,7 +117,7 @@ The advanced setup for {% data variables.product.prodname_code_scanning %} is he
 {% data reusables.repositories.navigate-to-repo %}
 {% data reusables.repositories.actions-tab %}
 1. If the repository has already at least one workflow configured and running, click **New workflow** to display starter workflows. If there are currently no workflows configured for the repository, go to the next step.
-   ![Screenshot of the Actions tab for a repository. The "New workflow" button is highlighted with an orange outline](/assets/images/help/security/actions-new-workflow-button.png)
+   ![Screenshot of the Actions tab for a repository. The "New workflow" button is highlighted with an orange outline.](/assets/images/help/security/actions-new-workflow-button.png)
 2. In the "Choose a workflow" or "Get started with {% data variables.product.prodname_actions %}" view, scroll down to the "Security" category and click **Configure** under the workflow you want to configure. You may need to click **View all** to find the security workflow you want to configure.
    ![Screenshot of the Security category of starter workflows. The Configure button and "View all" link are highlighted with an orange outline.](/assets/images/help/security/actions-workflows-security-section.png)
 3. Follow any instructions in the workflow to customize it to your needs. For more general assistance about workflows, click **Documentation** on the right pane of the workflow page.
@@ -261,7 +261,7 @@ There are other situations where there may be no analysis for the latest commit
 
   To check whether a branch has been scanned, go to the {% data variables.product.prodname_code_scanning_caps %} page, click the **Branch** drop-down and select the relevant branch.
 
-  ![Choose a branch from the Branch drop-down menu](/assets/images/help/repository/code-scanning-branch-dropdown.png)
+  ![Choose a branch from the Branch drop-down menu.](/assets/images/help/repository/code-scanning-branch-dropdown.png)
 
   The solution in this situation is to add the name of the base branch to the `on:push` and `on:pull_request` specification in the {% data variables.product.prodname_code_scanning %} workflow on that branch and then make a change that updates the open pull request that you want to scan.