Updated CI Pipelines (markdown)

CI-Pipelines.md

@@ -26,8 +26,8 @@ _Beware that some behaviors (e.g. file path case sensitivities) differ between O
 
 If the `license/cla` check hangs (takes more than about 1 minute), try closing/reopening your PR.
 
-## CI Pipeline for master/release branch Validation
+## CI Pipeline for main/release branch Validation
 
-Once a change is merged into `master` or a `release` branch, the CI loop kicks off several builds and other checks, similar to the PR checks.  Microsoft employees can view these runs [here](https://offnet.visualstudio.com/officenet/_build).  To monitor the official build for a particular commit, just look for the pipeline runs labeled something like "Individual CI for master" with the commit message also listed.
+Once a change is merged into `main` or a `release` branch, the CI loop kicks off several builds and other checks, similar to the PR checks.  Microsoft employees can view these runs [here](https://offnet.visualstudio.com/officenet/_build).  To monitor the official build for a particular commit, just look for the pipeline runs labeled something like "Individual CI for main" with the commit message also listed.
 
 Once the relevant build has succeeded, you may update a dependency on the built packages to the pre-release version (ending in `-0`) and run `npm i` at which point you'll be pulling in the pre-release version of the dependency containing the change in question.