Update Branch Names in CONTRIBUTING

Author: oleibman

CONTRIBUTING.md

@@ -43,7 +43,7 @@ This makes it easier to see exactly what is being tested when reviewing the PR.
 4. By default, Github removes markdown headings in the Release Notes. You can either edit to restore these, or, probably preferably, change the default comment character on your system - `git config core.commentChar ";"`.
 
 > **Note:** Tagged releases are made from the `master` branch. Only in an emergency should a tagged release be made from the `release` branch. (i.e. cherry-picked hot-fixes.) However, there are 4 branches which have been updated to apply security patches, and those may be tagged if future security updates are needed.
-- release1291 (no further updates aside from security patches, including code changes needed for Php 8.5 compatibility)
-- release210 (no further updates aside from security patches, including code changes needed for Php 8.5 compatibility)
-- release222
-- release390
+- 1.30.x (no further updates aside from security patches, including code changes needed for Php 8.5 compatibility)
+- 2.1.x (no further updates aside from security patches, including code changes needed for Php 8.5 compatibility)
+- 2.4.x
+- 3.10.x