message: Update CONTRIBUTING.md
  updates for master --> main rename
diff: what you are trying to add/fix. That way, we can also offer suggestions or
  let you know if there is already an effort in progress.
  1. Fork this repository.
  -1. Create a _topic_ branch in your fork based on the correct branch (usually the **develop** branch, see [Branches section](#branches) below). Note, this step is recommended but technically not required if contributing using a fork.
  +1. Create a _topic_ branch in your fork based on the main branch. Note, this step is recommended but technically not required if contributing using a fork.
  1. Edit the code in your fork.
  1. Write appropriate tests for your changes. Try to achieve at least 95% code coverage on any new code. No pull request will be accepted without unit tests.
  1. Sign CLA (see [CLA](#cla) below).
  @@ -20,10 +20,10 @@ Agreement. You can do so by going to https://cla.salesforce.com/sign-cla.
  ## Branches
  -- We work in `develop`.
  -- Our released (aka. _production_) branch is `master`.
  +- We work in branches off of `main`.
  +- Our released (aka. _production_) branch is `main`.
  - Our work happens in _topic_ branches (feature and/or bug-fix).
  - - feature as well as bug-fix branches are based on `develop`
  + - feature as well as bug-fix branches are based on `main`
  - branches _should_ be kept up-to-date using `rebase`
  - [commit messages are enforced](DEVELOPING.md#When-you-are-ready-to-commit)
  - see below for further merge instructions
  @@ -36,24 +36,11 @@ Agreement. You can do so by going to https://cla.salesforce.com/sign-cla.
  - _Topic_ branches are:
  - 1. based on `develop` and will be
  - 1. squash-merged into `develop`.
  + 1. based on `main` and will be
  + 1. squash-merged into `main`.
  -- Hot-fix branches are an exception.
  - - Instead we aim for faster cycles, and a generally stable `develop` branch.
  -
  -### Merging `develop` into `master`
  -
  -- When a development cycle finishes, the content of the `develop` branch will become the `master` branch
  -
  -```
  -$ git checkout master
  -$ git reset --hard develop
  -$
  -$ # Using a custom commit message for the merge below
  -$ git merge -m 'Merge -s our (where _ours_ is develop) releasing stream x.y.z.' -s ours origin/master
  -$ git push origin master
  -```
  +### Releasing
  +- A new version of this library will be published upon merging PRs to `main`, with the version number increment based on commitizen.
  ## Pull Requests
  