Use boldface for clickable UI elements (#32201)

hsnabszhdn · nguyenalex836 · web-flow · commit 244e4cbbfcab · 2024-03-25T17:18:24.000Z
Co-authored-by: Alex Nguyen &lt;150945400+nguyenalex836@users.noreply.github.com&gt;
diff --git a/content/admin/identity-and-access-management/reconfiguring-iam-for-enterprise-managed-users/migrating-from-saml-to-oidc.md b/content/admin/identity-and-access-management/reconfiguring-iam-for-enterprise-managed-users/migrating-from-saml-to-oidc.md
@@ -54,9 +54,9 @@ To migrate your enterprise from SAML to OIDC, you will disable your existing {%
 {% data reusables.emus.use-enterprise-recovery-code %}
 {% data reusables.enterprise-accounts.security-tab %}
 1. At the bottom of the page, next to "Migrate to OpenID Connect single sign-on", click **Configure with Azure**.
-1. Read the warning, then click "I understand, begin migrating to OpenID Connect".
+1. Read the warning, then click **I understand, begin migrating to OpenID Connect**.
 {% data reusables.enterprise-accounts.emu-azure-admin-consent %}
-1. After you grant consent, a new browser window will open to {% data variables.location.product_location %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click "Enable OIDC authentication".
+1. After you grant consent, a new browser window will open to {% data variables.location.product_location %} and display a new set of recovery codes for your {% data variables.enterprise.prodname_emu_enterprise %}. Download the codes, then click **Enable OIDC authentication**.
 1. Wait for the migration to complete, which can take up to an hour. To check the status of the migration, navigate to your enterprise's authentication security settings page. If "Require SAML authentication" is selected, the migration is still in progress.
 
    {% warning %}
diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md
@@ -43,7 +43,7 @@ An administrator needs to register your LMS instance with classroom before you c
 
 1. Sign into [Canvas](https://www.instructure.com/canvas/#login).
 1. Select the Canvas course to integrate with {% data variables.product.prodname_classroom %}.
-1. Click "Settings" in the left sidebar, then click the "Apps" tab.
+1. Click **Setting** in the left sidebar, then click the **Apps** tab.
 1. Click the **+ App** button.
 1. Under "Configuration Type", select **By Client ID** from the dropdown menu.
 1. Under "Client ID", input the Client ID that your LMS administrator created when registering your LMS instance with {% data variables.product.prodname_classroom %}.
diff --git a/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md b/content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/troubleshooting-your-migration-with-github-enterprise-importer.md
@@ -115,7 +115,7 @@ To resolve this issue, set the `--bbs-shared-home` argument for `gh bbs2gh migra
 You can identify the shared home directory in Bitbucket Server.
 
 1. Navigate to the Administration area of your Bitbucket Server or Data Center instance.
-1. In the sidebar, under "System," click "Storage."
+1. In the sidebar, under "System," click **Storage**.
 1. Under "Shared directory," view the location of your server's shared home directory.
 
 If you're running Bitbucket Data Center in cluster mode with multiple notes, your shared directory will be shared between cluster nodes and should be mounted in the same location on each node.
diff --git a/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md b/content/repositories/viewing-activity-and-data-for-your-repository/using-the-activity-view-to-see-changes-to-a-repository.md
@@ -27,7 +27,7 @@ For each activity, you can view the exact changes by clicking "Compare changes."
      ![Screenshot of a repository's branches view. To the right of a branch, the pulse icon is highlighted with a dark orange outline.](/assets/images/help/graphs/activity-view-icon.png)
 
 1. Use the dropdown menus to filter the activity view.
-   - To see activity on a particular branch, select the **{% octicon "git-branch" aria-hidden="true" %} BRANCH NAME** dropdown menu, then click a branch name. Alternatively, within the dropdown menu, start typing a branch name into the search field. To view activity across all branches in the repository, click "View activity for all branches".
+   - To see activity on a particular branch, select the **{% octicon "git-branch" aria-hidden="true" %} BRANCH NAME** dropdown menu, then click a branch name. Alternatively, within the dropdown menu, start typing a branch name into the search field. To view activity across all branches in the repository, click **View activity for all branches**.
 
    - To filter by activity type, select the **{% octicon "pulse" aria-hidden="true" %} All activity** dropdown menu, then click an activity type. You can choose to display direct pushes, pull request merges, force pushes, branch creations, and branch deletions.
 
diff --git a/data/reusables/advanced-security/secret-scanning-push-protection-enterprise.md b/data/reusables/advanced-security/secret-scanning-push-protection-enterprise.md
@@ -2,7 +2,7 @@
 
    ![Screenshot of the "Push protection" section of the "Code security and analysis" page. Two buttons, labeled "Enable all" and "Disable all", are highlighted with a dark orange outline.](/assets/images/enterprise/security/secret-scanning-enable-push-protection-enterprise.png)
 
-1. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion secret-scanning-custom-link-on-block %}
+1. Optionally, click **Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}**.{% ifversion secret-scanning-custom-link-on-block %}
 1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, click **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
 
    ![Screenshot of the "Push protection" section of the "Code security and analysis" page. The "Add a resource link in the CLI and web UI when a commit is blocked" checkbox and the custom link text field are highlighted with a dark orange outline.](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}
diff --git a/data/reusables/advanced-security/secret-scanning-push-protection-org.md b/data/reusables/advanced-security/secret-scanning-push-protection-org.md
@@ -1,5 +1,5 @@
 1. Under "{% data variables.product.prodname_secret_scanning_caps %}", under "Push protection", click **Enable all**.
-1. Optionally, click "Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}."{% ifversion push-protection-custom-link-orgs %}
+1. Optionally, click **Automatically enable for repositories added to {% data variables.product.prodname_secret_scanning %}**.{% ifversion push-protection-custom-link-orgs %}
 1. Optionally, to include a custom link in the message that members will see when they attempt to push a secret, select **Add a resource link in the CLI and web UI when a commit is blocked**, then type a URL, and click **Save link**.
 
    ![Screenshot of the "Push protection" section of the "Code security and analysis" page. The "Add a resource link in the CLI and web UI when a commit is blocked" checkbox and the custom link text field are highlighted with a dark orange outline.](/assets/images/help/organizations/secret-scanning-custom-link.png){% endif %}
diff --git a/data/reusables/apps/accept_new_permissions_steps.md b/data/reusables/apps/accept_new_permissions_steps.md
@@ -1,2 +1,2 @@
 1. Click **Save changes** at the bottom of the page.
-1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations). You'll see a link under the app name, letting you know that the app is requesting different permissions. Click "Review request", and then click "Accept new permissions."
+1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations). You'll see a link under the app name, letting you know that the app is requesting different permissions. Click **Review request**, and then click **Accept new permissions**.

Original file line number	Diff line number	Diff line change
`@@ -1,2 +1,2 @@`
`1`	`1`	`1. Click Save changes at the bottom of the page.`
`2`		-1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations). You'll see a link under the app name, letting you know that the app is requesting different permissions. Click "Review request", and then click "Accept new permissions."
	`2`	+1. If you've installed the app on your account, check your email and follow the link to accept the new permissions. Any time you change your app's permissions or webhooks, users who have installed the app (including yourself) will need to accept the new permissions before the changes take effect. You can also accept the new permissions by navigating to your [installations page](https://github.com/settings/installations). You'll see a link under the app name, letting you know that the app is requesting different permissions. Click Review request, and then click Accept new permissions.