[develop] Update SRW reference chapter

[selbigmtnwx23]

• Update develop to head at ufs-community

• Use this template to give a detailed message describing the change you want to make to the code.

• You may delete any sections labeled "optional" and any instructions within .

• If you are unclear on what should be written here, see https://github.com/wrf-model/WRF/wiki/Making-a-good-pull-request-message for some guidance and review the Code Contributor's Guide at https://github.com/ufs-community/ufs-srweather-app/wiki/Code-Manager's-Guide.

• Code reviewers will assess the PR based on the criteria laid out in the Code Reviewer's Guide (https://github.com/ufs-community/ufs-srweather-app/wiki/Code-Manager's-Guide).

• The title of this pull request should be a brief summary (ideally less than 100 characters) of the changes included in this PR. Please also include the branch to which this PR is being issued (e.g., "[develop]: Updated UFS_UTILS hash").

• Use the "Preview" tab to see what your PR will look like when you hit "Create pull request"

--- Delete this line and those above before hitting "Create pull request" ---

DESCRIPTION OF CHANGES:

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

TESTS CONDUCTED:

• derecho.intel
• gaea.intel
• gaea-c6.intel
• hera.gnu
• hera.intel
• hercules.intel
• jet.intel
• orion.intel
• wcoss2.intel
• NOAA Cloud (indicate which platform)
• Jenkins
• fundamental test suite
• comprehensive tests (specify which if a subset was used)

DEPENDENCIES:

DOCUMENTATION:

ISSUE:

CHECKLIST

• My code follows the style guidelines in the Contributor's Guide
• I have performed a self-review of my own code using the Code Reviewer's Guide
• I have commented my code, particularly in hard-to-understand areas
• My changes need updates to the documentation. I have made corresponding changes to the documentation
• My changes do not require updates to the documentation (explain).
• My changes generate no new warnings
• New and existing tests pass with my changes
• Any dependent changes have been merged and published

LABELS (optional):

A Code Manager needs to add the following labels to this PR:

• Work In Progress
• bug
• enhancement
• documentation
• release
• high priority
• run_ci
• run_we2e_fundamental_tests
• run_we2e_comprehensive_tests
• Needs Cheyenne test
• Needs Jet test
• Needs Hera test
• Needs Orion test
• help wanted

CONTRIBUTORS (optional):

[MichaelLueken]

@selbigmtnwx23 -

Thanks for adding the updates from the Technical-FAQs site to the SRW App's documentation!

I do have two concerns:

1. The .. _AddPhys: entry on line 209 should be moved down to after the newly added frequently asked questions so that it matches up with the add physics scheme FAQ.
2. The devclean.sh convenience script has changed and --clean is no longer an option. I have provided a suggested change for this FAQ entry.

Following these modifications, I should be able to provide my approval to for this PR.

[MichaelLueken]

The failed Doc Tests won't keep this PR from getting merged. The security certificate for the https://www.fvcom.org/ site has expired and the failure isn't due to changes in this PR.

[MichaelLueken]

@selbigmtnwx23 -

Thanks for applying the modifications related to the devclean.sh convenience script! The updates look good to me, so I will go ahead and approve these now.

[jdkublnick]

Missing comma after Derecho