update cloud release schedule (#8903)

https://docs.google.com/document/d/1WXfmyBsGlIoJvSdxaEhV0iYTD4ylm9ykLyJItDE53eE/edit

content/departments/cloud/technical-docs/index.md

@@ -17,7 +17,9 @@ The release process is performed in steps:
 1. New version is released via [release team](../../engineering/teams/release/team/index.md)
 2. GitHub issue in [Sourcegraph Customer repository](https://github.com/sourcegraph/customer) with the `mi2 env create-tracking-issue -e prod $TARGET_VERSION` command
 3. GitHub issue is labeled with `team/cloud` and Cloud Team is automatically notified to perform Managed Instances upgrade. Label is part of the template.
-4. Cloud team performs upgrade of all instances in given order:
+4. Cloud team performs upgrade of all instances in given order depending on the release type:
+
+#### Release process for quarterly major release
 
 | Stage | Working days since release | Action                                                                                                                               | Condition not met?                                                              |
 | ----- | -------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
@@ -34,7 +36,7 @@ Sample upgrade:
 - [tracking issue - 5.1.4](https://github.com/sourcegraph/customer/issues/2251).
 - GitHub Pull Requests for [5.1.4 upgrade](https://github.com/sourcegraph/cloud/pulls?q=is%3Apr+is%3Aclosed+label%3Ami-upgrade+5.1.4)
 
-#### Release process for patch releases
+#### Release process for monthly minor or patch releases
 
 With [bi-weekly patch release schedule](../../engineering/dev/process/releases/index.md#patch-schedule), Cloud Team is using simplified release process to ensure Cloud customers can obtain patch as soon as possible.