Merge branch 'sam.white-master-patch-29723' into 'master'

Fix documentation header

See merge request !139283



Merged-by: Evan Read <eread@gitlab.com>
Approved-by: Nate Rosandich <nrosandich@gitlab.com>
Co-authored-by: Sam White <swhite@gitlab.com>

doc/administration/audit_event_streaming/examples.md

@@ -40,7 +40,7 @@ X-Gitlab-Event-Streaming-Token: <DESTINATION_TOKEN>
 X-Gitlab-Audit-Event-Type: repository_git_operation
 ```
 
-### Example payloads for SSH events
+### Example payloads for Git over SSH events
 
 Fetch:
 
@@ -106,7 +106,7 @@ Push:
 }
 ```
 
-### Example payloads for SSH events with Deploy Key
+### Example payloads for Git over SSH events with Deploy Key
 
 > [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/363876) in GitLab 15.3.
 
@@ -142,7 +142,7 @@ Fetch:
 }
 ```
 
-### Example payloads for HTTP and HTTPS events
+### Example payloads for Git over HTTP and HTTPS events
 
 Fetch:
 
@@ -208,7 +208,7 @@ Push:
 }
 ```
 
-### Example payloads for HTTP and HTTPS events with Deploy Token
+### Example payloads for Git over HTTP and HTTPS events with Deploy Token
 
 Fetch:
 

doc/user/project/deploy_keys/index.md

@@ -65,7 +65,7 @@ As with all sensitive information, you should ensure only those who need access
 For human interactions, use credentials tied to users such as Personal Access Tokens.
 
 To help detect a potential secret leak, you can use the
-[Audit Event](../../../administration/audit_event_streaming/examples.md#example-payloads-for-ssh-events-with-deploy-key) feature.
+[Audit Event](../../../administration/audit_event_streaming/examples.md#example-payloads-for-git-over-ssh-events-with-deploy-key) feature.
 
 ## View deploy keys