update howtocommit

Author: james-bruten-mo

source/Reviewers/howtocommit.rst

@@ -51,7 +51,7 @@ are more complicated conflicts ask the developer to solve them themselves. If
 there are conflicts in versions.py then see the details in the macro section
 below.
 
-Then checkout the up to date branch, eg.
+Then switch to the up to date branch, eg.
 
 .. code-block::
 
@@ -130,7 +130,7 @@ rose-stem app then you will need to upgrade the test-suite.
 
             .. note::
 
-                All LFRic Core tickets with macros are expected to be linked with LFRic Apps, though they may not have required an LFRic Apps development branch (although an Apps ticket should be provided). This is fine - if there is no LFRic Apps branch just checkout the LFRic Apps trunk. Then run the apply_macros script as described above and this will share the upgrade macro across both LFRic Apps and LFRic Core as needed.
+                All LFRic Core tickets with macros are expected to be linked with LFRic Apps, though they may not have required an LFRic Apps development branch (although an Apps ticket should be provided). This is fine - if there is no LFRic Apps branch just checkout the LFRic Apps main. Then run the apply_macros script as described above and this will share the upgrade macro across both LFRic Apps and LFRic Core as needed.
 
     .. important::
 
@@ -283,7 +283,7 @@ are no clashes with what else has gone on trunk.
         .. code-block:: RST
 
             git pull
-            git checkout <branch name>
+            git switch <branch name>
             cd <path_to>/user_guide/doc
             conda activate jules-user-guide
             make html

source/WorkingPractices/forking.rst

@@ -94,8 +94,8 @@ Most work to maintain a fork involves syncing it with the upstream repository. S
 
         .. code-block::
 
-            # Checkout the desired branch
-            git checkout main
+            # Change to the desired branch
+            git switch main
 
             # Merge in changes from the upstream
             git merge upstream/main

source/WorkingPractices/gh_dev_init.rst

@@ -41,7 +41,9 @@ There is no requirement to open an issue before making a pull request, as long a
 Clone the Repository
 --------------------
 
-A clone is a local copy of a repository - you can have a local clone of either an upstream repository or a fork. A clone will have an active branch which will initially be the default branch of the repository. All other branches in the repository can be accessed using the ``checkout`` command (see below). For general development, you should now get a clone of your fork.
+A clone is a local copy of a repository - you can have a local clone of either
+an upstream repository or a fork. A clone will have an active branch which will
+initially be the default branch of the repository. All other branches in the repository can be accessed using the ``switch`` command (see below). For general development, you should now get a clone of your fork.
 
 .. tip::
 
@@ -122,13 +124,13 @@ To create a branch and switch to it from the command line, the syntax is,
         .. code-block::
 
             # parent_branch will default to the current branch if not provided
-            # switch will automatically checkout the newly created branch
+            # switch will automatically change to the newly created branch
             git switch -c <branch_name> [<parent_branch>]
 
             # Or
 
             git branch <branch_name> <source_branch>
-            git checkout <branch_name>
+            git switch <branch_name>
 
 Developing a Change
 -------------------