docs: Clarify documentation for repository comment_strategy

Add a more general "controlling comment volume" section with Github
and Gitlab subsections to clarify the shared semantics

Author: aThorp96

docs/content/docs/guide/repositorycrd.md

@@ -126,7 +126,27 @@ right to merge commits to the default branch can change the PipelineRun and have
 access to the infrastructure.
 {{< /hint >}}
 
-## Disabling all comments for PipelineRuns on GitLab MR
+## Controlling Pull/Merge Request comment volume
+
+For GitHub (Webhook) and GitLab integrations, you can control the types
+of Pull/Merge request comments which Pipelines as Code emits using
+the `spec.<provider>.comment_strategy` setting. This can
+help reduce notification volume for Repositories which use long-lasting
+Pull/Merge requests with many PipelineRuns.
+
+Acceptable values for `spec.<provider>.comment_strategy` are `""`
+(default) and `"disable_all"`.
+
+When you set the value of `comment_strategy` to `disable_all` Pipelines
+as Code will not add any comment on the Pull/Merge Request related to
+PipelineRun status.
+
+Note: The `disable_all` strategy applies only to comments about a
+PipelineRun's status (e.g., "started," "succeeded"). Comments may still
+appear if there are errors validating PipelineRuns in the `.tekton`
+directory. (See [Running the PipelineRun docs](../running/#errors-when-parsing-pipelinerun-yaml) for details)
+
+### GitLab
 
 By default, Pipelines-as-Code attempts to update the commit status through the
 GitLab API. It first tries the source project (fork), then falls back to the
@@ -149,8 +169,6 @@ Comments are only posted when:
 - The event type and repository settings allow commenting
 - The `comment_strategy` is not set to `disable_all`
 
-To explicitly disable all comments on GitLab Merge Requests for a Repository,
-use the `comment_strategy` setting:
 
 ```yaml
 spec:
@@ -159,9 +177,7 @@ spec:
       comment_strategy: "disable_all"
 ```
 
-## Disabling all comments for PipelineRuns in GitHub Pull Requests on GitHub Webhook Setup
-
-`comment_strategy` allows you to disable the comments on GitHub PR for a Repository
+### GitHub Webhook
 
 ```yaml
 spec:
@@ -170,11 +186,6 @@ spec:
       comment_strategy: "disable_all"
 ```
 
-When `comment_strategy` is set to `disable_all` Pipelines as Code will not create any comment on the pull request for PipelineRun Status
-
-Note: The disable_all strategy applies only to comments about a PipelineRun's status (e.g., "started," "succeeded").
-If your PipelineRun YAML definition fails validation, a comment detailing the error will always be posted to the pull request. [see docs](../running/#errors-when-parsing-pipelinerun-yaml)
-
 ## Concurrency
 
 `concurrency_limit` allows you to define the maximum number of PipelineRuns running at any time for a Repository.