Merge pull request #627 from linear-b/LINBEE-13204-add-cm-repo-to-doc

Update bitbucket-installation.md

Author: PavelLinearB

docs/bitbucket-installation.md

@@ -18,34 +18,35 @@ description: Install gitStream to your Bitbucket workspace.
 Bitbucket Installation Overview
 
 1. Designate a gitStream user account.
-2. Create a CM configuration file.
+2. Create a `cm` repo and `.cm` configuration file.
 3. Create a Bitbucket pipeline.
 4. Install the gitStream service.
 
 ## Designate a gitStream User Account
 
 gitStream automation rules are executed on behalf of the user account configured when you install the gitStream service. This account must have the necessary permissions to the relevant repositories.
 
-We recommend creating a dedicated service account to control access to individual repositories easily. You can also use your professional or personal Bitbucket account for this, which would result in all automations being executed under that account.
+We recommend creating a dedicated service account to easily control access to individual repositories. You can also use your professional or personal Bitbucket account for this, resulting in all automations being executed under that account.
 
 !!! tip "Use this account when you integrate gitStream"
     Make sure to use this account when authorizing Bitbucket in LinearB.
 
-## Create a CM Configuration File
+## Create a `cm` repo and `.cm` configuration file.
 
-Create a `gitstream.cm` rules file in the root directory of your repository's default branch (usually `master` or `main`). This file will contain a YAML configuration that determines the workflows that run on your repositories. You can name the CM file anything you want as long as it ends in `.cm`.
-
-!!! info "Configuration files go in the repo's root directory."
-    Your `.cm` files should be placed in the repository's root directory.
+Create a `cm` repository in your Bitbucket workspace. This repository must reside in the same project as your target repositories. In the root directory of the default branch (usually `master` or `main`), create a `gitstream.cm` rules file to define the workflow automations. The file can have any name but must end with the `.cm` extension.
 
+!!! info "Configuration File Locations"
+	Group-level rules require your `.cm` files to be placed in the `cm` repository's root directory.
+	You can also define specific repo-level rules under the `.cm` folder in each of the connected repositories
+ 
 !!! example "Example Configuration"
     ```yaml
     --8<-- "docs/downloads/gitstream-bb.cm"
     ```
 
 ## Create a Bitbucket Pipeline
 
-Once your gitStream configuration file is set up, you need a Bitbucket Pipelines configuration file to trigger gitStream automations. Create a `bitbucket-pipelines.yml` file in your repository's default branch (usually `master` or `main`) and add the following configuration:
+Once your gitStream configuration file is set up, you need a Bitbucket Pipelines configuration file to trigger gitStream automations. Create a `bitbucket-pipelines.yml` file in your `cm` repository's default branch and add the following configuration:
 
 ```yaml
 --8<-- "docs/downloads/bitbucket-pipelines.yml"

docs/gitlab-installation.md

@@ -13,7 +13,7 @@ description: Install gitStream to your GitLab organization.
 GitLab Installation Overview
 
 1. Designate a gitStream user account.
-1. Create a CM configuration file.
+1. Create a `cm` repo and `.cm` configuration file.
 1. Create a GitLab pipeline.
 1. Install the gitStream service. 
 
@@ -26,15 +26,13 @@ We recommend creating a [dedicated service account](https://docs.gitlab.com/ee/u
 !!! tip "Use this account when you integrate gitStream"
     Make sure to use this account when authorizing GitLab in LinearB.
 
-## Create a `cm` repo and a CM Configuration File
+## Create a `cm` repo and `.cm` configuration file.
 
-Group rules are ideal when you want to enforce consistent rules across every repo in your GitLab group. You can define them by creating a special repository named `cm` in the parent group for the git repositories on which you want to run gitStream. Here, you can add automation files that apply to **all** repositories within that group that are connected to gitStream.
+Create a `cm` project (repository) in your GitLab group. This repository must be created in the same group or parent group as the target repositories. In the root directory of the default branch (usually `master` or `main`), create a `gitstream.cm` rules file to define the workflow automations. The file name can vary but must end in `.cm`.
 
-Create a `cm` project (repository) in your GitLab group, and create a `gitstream.cm` rules file in the root directory of your `cm` repository's default branch (usually `master` or `main`). This file will contain a YAML configuration that determines the workflows that run on your organization's repos. You can name the CM file anything you want as long as it ends in `.cm`
-
-!!! info "Configuration files go in the repo's root directory."
-	Group-level rules require your `.cm` files to be placed in the repository's root directory.
-	You can also define specific repo-level rules under the `.cm` folder in each of the connected repositories
+!!! info "Configuration File Locations"
+	Group-level rules require your `.cm` files to be placed in the `cm` repository's root directory.
+	You can also define specific repo-level rules under the `.cm` folder in each of the connected repositories.
 
 !!! example "Example Configuration"
 		--8<-- "docs/downloads/gitstream.cm"