Line edits

Author: lootle1

learn-pr/github/configure-use-secret-scanning-github-repository/includes/1-introduction.md

@@ -2,7 +2,7 @@ GitHub's security features help keep code and secrets secure in repositories and
 
 Imagine that you're the administrator of a GitHub project involving several repositories that communicate with multiple external services. You'd like to make sure that no authentication credentials for these services get committed in the repositories of the project. Luckily, your company just purchased a GitHub Advanced Security license that includes secret scanning, a GitHub feature that does just that!
 
-To configure and use secret scanning for your project, you really need to understand what secret scanning is, how it works and the options available to you according to your use case.
+To configure and use secret scanning for your project, you really need to understand what secret scanning is, how it works, and the options available to you according to your use case.
 
 In this module, you'll learn about:
 

learn-pr/github/configure-use-secret-scanning-github-repository/includes/3-configure-secret-scanning.md

@@ -6,29 +6,20 @@ This unit walks you through the necessary steps to enable secret scanning at the
 
 Follow these steps to enable secret scanning and push protection on a private repository:
 
-1. In your repository, navigate to **Settings > Code security and analysis**.
-1. Select the **Enable** button next to **GitHub Advanced Security**
-1. Review the impact of enabling Advanced Security and select **Enable GitHub Advanced Security for this repository**.
-1. Select the **Enable** button next to **Secret scanning**. If you see a **Disable** button, it means that secret scanning was already enabled at organization level.
+1. In your repository, navigate to **Settings**.
+1. In the **Security** section select **Advanced Security**.
+1. Select the **Enable** button next to **Secret Protection**
+1. Review the impact of enabling and select **Enable Secret Protection**.
+1. If you see a **Disable** button, it means that secret scanning was already enabled at organization level.
 1. Select the **Enable** button next to **Push protection**.
 
 :::image type="content" source="../media/enable-secret-scanning-repo-settings.png" alt-text="Screenshot of secret scanning enabled in repository settings.":::
 
 ## Enable secret scanning for an organization
 
-Enabling secret scanning at the organization level ensures that secret scanning is enabled by default on all private repositories where GitHub Advanced Security is enabled.
+Enabling secret scanning at the organization level ensures that secret scanning is enabled by default on all private repositories where GitHub Advanced Security is enabled. In order to configure, you'll need to setup [GitHub Advanced Security](https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security).
 
-Follow these steps to enable secret scanning and push protection for an organization:
-
-1. In your organization, navigate to **Settings > Code security and analysis**.
-2. Select the **Enable all** button next to **GitHub Advanced Security**.
-3. Review the impact of enabling Advanced Security on all repositories and select **Enable all**.
-4. Select the **Enable all** button next to **Secret scanning** and select **Enable for eligible repositories**.
-   - (Optional) Select **Automatically enable for new public repositories and repositories with GitHub Advanced Security enabled**.
-5. Select the **Enable all** button next to **Push protection** and select **Enable for eligible repositories**.
-   - (Optional) Select **Automatically enable for repositories added to secret scanning**.
-
-:::image type="content" source="../media/enable-secret-scanning-org-settings.png" alt-text="Screenshot of enabling secret scanning in organization settings.":::
+Once setup, you can configure [Global Secret Scanning settings](https://docs.github.com/en/code-security/securing-your-organization/enabling-security-features-in-your-organization/configuring-global-security-settings-for-your-organization#configuring-global-secret-scanning-settings).
 
 ## Exclude files from being scanned
 
@@ -67,7 +58,7 @@ You'll receive an email notification if:
 
 ## Configure recipients of secret scanning alerts
 
-Repository and organization administrators can give view access to security alerts to people or teams who have write access to the repository under **Settings > Code security and analysis > Access to alerts**:
+Repository and organization administrators can give view access to security alerts to people or teams who have write access to the repository under **Settings > Security > Advanced Security > Access to Alerts**:
 
 :::image type="content" source="../media/access-to-alerts.png" alt-text="Screenshot of Access to alerts section with Search for people or teams field highlighted.":::