few tweaks, decided to not document iaf for now

Author: chrisb13

docs/models/run-a-model/run-access-om2.md

@@ -590,9 +590,9 @@ env:
 !!! warning
     This workflow is only for advanced users and provided to help users use COSIMA restart files with ACCESS-NRI executables for two key configurations. This workflow will use a mix of restart files: a spun ocean and a sea-ice model that has started almost from rest. This is physically inconsistent and so the model requires an extended spin up and re-evaluation to produce scientifically credible results. 
 
-As highlighted above in [Start the run from a specific restart file](/models/run-a-model/run-access-om/#specific-restart), there are situations where it is preferable to use an existing restart file rather than start the model from rest, e.g. when the configuration is very expensive to run. New ACCESS-NRI executables may be preferable to use because they contain bug fixes and a newer code base. However, in some cases, if the supplied restart file is not fully compatible with the model configuration, experiments using a custom restart file may require additional manual adjustments to run correctly. 
+As highlighted above in [start the run from a specific restart file](/models/run-a-model/run-access-om/#specific-restart), there are situations where it is preferable to use an existing restart file rather than start the model from rest, e.g. when the configuration is very expensive to run. New ACCESS-NRI executables may be preferable to use because they contain bug fixes and a newer code base. However, in some cases, if the supplied restart file is not fully compatible with the model configuration, experiments using a custom restart file may require additional manual adjustments to run correctly. 
 
-Here we provide a workflow for doing these manual adjustments for two key configurations, namely i) `release-01deg_jra55_ryf` and ii) `release-01deg_jra55_iaf`. The below gives instructions for `ryf` but it is essentially the same for `iaf`.
+Here we provide a workflow for doing these manual adjustments for a popular configuration, namely `release-01deg_jra55_ryf`. 
 
 We first need to identify the restart file we wish to use. For this example we will use `/g/data/cj50/access-om2/raw-output/access-om2-01/01deg_jra55v13_ryf9091/restart795`. It may be useful to consult [this forum thread](https://forum.access-hive.org.au/t/access-om2-control-experiments/258) for making this choice.
 
@@ -619,18 +619,18 @@ cp -r accessom2_restart.nml ocean /scratch/tm70/$USER/access-om2/restart_hackom2
 
 We then need to modify the payu configuration to restart from this mix of restart files, there are two steps:
 
-1. We tell CICE that it should not check the date of the restart file, this is because the `accessom2_restart.nml` file in the example above (folder `restart795`) is looking to start at `EXP_CUR_DATE    = 2100-01-01T00:00:00` which is not the start date the sea-ice model will have from the one we have just made above in `restart000`, it will have `1900-04-01T00:00:00`. For the first run you'll need to `set use_restart_time = .false.` in `ice/cice_in.nml`. After the first run, we suggest reverting `use_restart_time = .true.` in `ice/cice_in.nml` because having run the model once it will output correct dates on the new restart files. See `More complicated cases` [here](https://github.com/COSIMA/access-om2/wiki/Tutorials#updating-an-experiment) for further details.
+1. We tell CICE that it should not check the date of the restart file, this is because the `accessom2_restart.nml` file in the example above (folder `restart795`) is looking to start at `EXP_CUR_DATE    = 2100-01-01T00:00:00` which is not the start date the sea-ice model will have from the one we have just made above in `restart000`, it will have `1900-04-01T00:00:00`. For the first run you'll need to `set use_restart_time = .false.` in `ice/cice_in.nml`. For additional information, see `More complicated cases` in the [COSIMA/access-om2/wiki](https://github.com/COSIMA/access-om2/wiki/Tutorials#updating-an-experiment).
 
 2. Add the following two lines to `~/$USER/access-om2/release-01deg_jra55_ryf/config.yaml`:
 
 ```bash
 restart: 
   /scratch/tm70/$USER/access-om2/restart_hackom201ryf
 ```
-Finally, submit this new run with `payu run`. Once complete, don't forget to swap back the `ice/cice_in.nml`!
+Finally, submit this new run with `payu run`. 
 
 !!! tip
-    This has the same effect as adding `--restart FILE_NAME` to the `payu clone` command, as discussed above in [Start the run from a specific restart file](/models/run-a-model/run-access-om/#specific-restart)
+    This has the same effect as adding `--restart FILE_NAME` to the `payu clone` command, as discussed above in [start the run from a specific restart file](/models/run-a-model/run-access-om/#specific-restart)
 ### Edit a single {{ model }} component configuration
 
 Each of [{{ model }} components][model components] contains additional configuration options that are read in when the model component is running.<br>