Merge branch 'pw-sentence-case-secret-detection' into 'master'

Sentence-case secret detection

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/160796



Merged-by: Russell Dickenson <rdickenson@gitlab.com>
Approved-by: Russell Dickenson <rdickenson@gitlab.com>
Co-authored-by: phillipwells <pwells@gitlab.com>

doc/user/application_security/secret_detection/index.md

@@ -4,7 +4,7 @@ group: Secret Detection
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
 ---
 
-# Secret Detection
+# Secret detection
 
 DETAILS:
 **Tier:** Free, Premium, Ultimate
@@ -24,8 +24,8 @@ this risk, you should store your secrets outside your remote
 repositories. If a secret is exposed, you should revoke and replace it
 as soon as possible.
 
-Secret Detection scans your repository to help prevent your secrets
-from being exposed. Secret Detection scanning works on all text files,
+Secret detection scans your repository to help prevent your secrets
+from being exposed. Secret detection scanning works on all text files,
 regardless of the language or framework used.
 
 GitLab has three methods for detecting secrets, which can be used simultaneously:

doc/user/application_security/secret_detection/pipeline/index.md

@@ -160,7 +160,7 @@ Different features are available in different [GitLab tiers](https://about.gitla
 
 To enable pipeline secret detection, either:
 
-- Enable [Auto DevOps](../../../../topics/autodevops/index.md), which includes [Auto Pipeline Secret Detection](../../../../topics/autodevops/stages.md#auto-secret-detection).
+- Enable [Auto DevOps](../../../../topics/autodevops/index.md), which includes [Auto Secret Detection](../../../../topics/autodevops/stages.md#auto-secret-detection).
 
 - [Edit the `.gitlab-ci.yml` file manually](#edit-the-gitlab-ciyml-file-manually). Use this method
   if your `.gitlab-ci.yml` file is complex.
@@ -188,7 +188,7 @@ your GitLab CI/CD configuration file is complex.
 1. In the **Branch** text box, enter the name of the default branch.
 1. Select **Commit changes**.
 
-Pipelines now include a pipeline Secret Detection job.
+Pipelines now include a pipeline secret detection job.
 
 #### Use an automatically configured merge request
 
@@ -207,7 +207,7 @@ To enable pipeline secret detection:
 
 1. On the left sidebar, select **Search or go to** and find your project.
 1. Select **Secure > Security configuration**.
-1. In the **Pipeline Secret Detection** row, select **Configure with a merge request**.
+1. In the **Pipeline secret detection** row, select **Configure with a merge request**.
 1. Optional. Complete the fields.
 1. Select **Create merge request**.
 1. Review and merge the merge request.
@@ -844,7 +844,7 @@ Below is a table with the demonstration projects and their associated workflows:
 
 There are also some video demonstrations walking through setting up remote rulesets:
 
-- [Secret Detection with local and remote ruleset](https://youtu.be/rsN1iDug5GU)
+- [Secret detection with local and remote ruleset](https://youtu.be/rsN1iDug5GU)
 
 ## FIPS-enabled images
 

doc/user/application_security/secret_detection/secret_push_protection/index.md

@@ -69,7 +69,7 @@ Prerequisites:
 1. Sign in to your GitLab instance as an administrator.
 1. On the left sidebar, at the bottom, select **Admin**.
 1. Select **Settings > Security and compliance**.
-1. Under **Secret Detection**, select or clear **Allow secret push protection**.
+1. Under **Secret detection**, select or clear **Allow secret push protection**.
 
 ### Enable secret push protection in a project