Feature 898 headers

[lisagoodrich]

Pull Request Testing

• [x] Describe testing already performed for these changes:
  This was a big adventure. All of the headers for the different sections: Contributor's Guide, User's Guide, Release Guide and Verification Dataset Guide have been updated. In some cases, the text within the headers has been capitalized for consistency. Three changes were made in the glossary.rst file to update notes to warnings for consistency: POINT_STAT_GRID POINT_STAT_POLY PB2NC_POLY I compared the feature_898_headers branch https://metplus.readthedocs.io/en/feature_898_headers/Users_Guide/index.html to the development branch in ReadTheDocs https://metplus.readthedocs.io/en/develop/Users_Guide/index.html. I did this for ALL of the above sections. In some cases, I opened up the files in GitHub to confirm that the new and correct headers were being used. https://github.com/dtcenter/METplus/tree/feature_898_headers/docs

The only area where I didn't check the headers was here: https://metplus.readthedocs.io/en/feature_898_headers/generated/met_tool_wrapper/index.html and here: https://metplus.readthedocs.io/en/feature_898_headers/generated/model_applications/index.html I do not know where these files are being generated.

REMINDER: Please keep the issue open. The MET headers need to be finished before this issue can close.

• [X] Recommend testing for the reviewer(s) to perform, including the location of input datasets, and any additional instructions:
  I feel very confident that these headers are correct. However, this was a tedious and complex process. I really struggled on the Release Guide. There are over 100 files that link to many different directories. This formatting also assumes the file sections will be at the SAME level across different tools. So far, this is the case. Please do a spot check of the headers as you see fit. George asked to be included on this pull request. Since is working in METplus.

• [x] Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes, there are no errors.]

• [x] Do these changes include sufficient testing updates? [Yes]

• [x] Will this PR result in changes to the test suite? [No]
  If yes, describe the new output and/or changes to the existing output:
  

• [x] Please complete this pull request review by 11/3/23.
  

Pull Request Checklist

See the METplus Workflow for details.

• [ ] Add any new Python packages to the METplus Components Python Requirements table.
• [x] Review the source issue metadata (required labels, projects, and milestone).
• [x] Complete the PR definition above.
• [x] Ensure the PR title matches the feature or bugfix branch name.
• [x] Define the PR metadata, as permissions allow. Select: Reviewer(s) Select: Organization level software support Project or Repository level development cycle Project Select: Milestone as the version that will include these changes
• [x] After submitting the PR, select the :gear: icon in the Development section of the right hand sidebar. Search for the issue that this PR will close and select it, if it is not already selected.
• [ ] After the PR is approved, merge your changes. If permissions do not allow this, request that the reviewer do the merge.
• [ ] Close the linked issue and delete your feature or bugfix branch from GitHub.

[georgemccabe]

I only reviewed the User's Guide content to make sure there are no conflicts with my changes since I am working on those files. I don't see anything of concern, but I did find a minor typo (see suggested change).