Line edits2

Author: lootle1

learn-pr/github/configure-use-secret-scanning-github-repository/5-exercise.yml

@@ -4,7 +4,7 @@ title: Exercise
 metadata:
   unitType: exercise
   title: Exercise - Exclude files from secret scanning
-  description: This exercise checks your knowledge on excluding files from being scanned by secret scanning. It's automatically graded via a workflow once you have completed the instructions.
+  description: This exercise checks your knowledge on excluding files from secret scanning. It's automatically graded via a workflow once you have completed the instructions.
   ms.date: 06/05/2025
   author: rmcmurray
   ms.author: robmcm

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

@@ -7,7 +7,7 @@ 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**.
-1. In the **Security** section select **Advanced Security**.
+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.
@@ -17,9 +17,9 @@ Follow these steps to enable secret scanning and push protection on a private re
 
 ## 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. 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).
+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 set up [GitHub Advanced Security](https://docs.github.com/en/get-started/learning-about-github/about-github-advanced-security).
 
-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).
+Once set up, 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
 
@@ -48,13 +48,13 @@ When a new secret is detected, GitHub notifies all users with access to security
 - Organization owners and enterprise owners, if they're administrators of repositories where secrets were leaked
 
 > [!NOTE]
-> Commit authors who've accidentally committed secrets will be notified, regardless of their notification preferences.
+> Commit authors who have accidentally committed secrets will be notified, regardless of their notification preferences.
 
 You'll receive an email notification if:
 
 - You're watching the repository.
 - You've enabled notifications for **All Activity** or for custom **Security alerts** on the repository.
-- In your notification settings, under "Subscriptions", then under "Watching", you have selected to receive notifications by email.
+- In your notification settings, under "Subscriptions," then under "Watching," you have selected to receive notifications by email.
 
 ## Configure recipients of secret scanning alerts
 

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

@@ -55,7 +55,7 @@ Follow these steps to create a custom pattern for a private repository:
 
 ### For an organization
 
-Follow the steps below to create a custom pattern for an organization:
+Follow the steps listed to create a custom pattern for an organization:
 
 1. In your organization, navigate to **Settings > Advanced Security > Global Settings**.
 1. Under **Custom patterns**, select **New pattern**.

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

@@ -8,9 +8,9 @@ Secret scanning is enabled by default on all public repositories and can be enab
 - Titles, descriptions, and comments in pull requests
 - Titles, descriptions, and comments in GitHub Discussions
 
-GitHub will alert you when secrets are detected so the appropriate actions can be taken to secure your code according to the type of secret that was committed. And with push protection enabled, secret leaks can be prevented by blocking commits that contain known secrets. 
+GitHub will alert you when secrets are detected so the appropriate actions can be taken to secure your code according to the type of secret that was committed. And with push protection enabled, secret leaks can be prevented by blocking commits that contain known secrets.
 
-For private repositories, the secret scanning configuration options also enable you to exclude specific files from scans, choose the people to notify of alerts, and create custom patterns for the secrets in your project that aren't automatically detected by GitHub.
+For private repositories, the secret scanning configuration options also enable you to exclude specific files from scans, choose the people to notify of alerts, and create custom patterns for the secrets in your project not automatically detected by GitHub.
 
 With secret scanning in GitHub, you can be aware of exposed secrets and respond accordingly to protect your assets.