GODRIVER-3550 Note that we typically merge into current release

Author: prestonvasquez

docs/CONTRIBUTING.md

@@ -53,7 +53,7 @@ PR [#1962](https://github.com/mongodb/mongo-go-driver/pull/1962) added the "Merg
 
 #### Regression
 
-If a regression is identified in the release/2.x branch, a fix should be submitted as a pull request targeting
+If a regression is identified in the release/2.x branch, a fix can be submitted as a pull request targeting
 release/2.x. Once this PR is merged, the "Merge up" GitHub Action will automatically create a pull request to merge
 release/2.x into release/2.x+1. This process is repeated until changes are merged all the way up to release/2.latest,
 which is then merged into the master branch.
@@ -105,6 +105,8 @@ gitGraph
    commit
 ```
 
+**Note**: In general, bug fixes should only target the latest release branch, since we only support patching the latest version. However, this is just a rule of thumb—exceptions can be made when necessary.
+
 #### Pull Request Management
 
 When the "Merge up" GitHub Action is enabled, multiple merge-up pull requests (such as PR1, PR2, and PR3) can be