Pointreg docs keywords.

[jrcain-usgs]

Description

Updated Pointreg examples with new keyword, and related descriptions and screenshots.

Related Issue

Fixes #5343 - pointreg examples use old keywords

How Has This Been Validated?

• Successfully ran each pointreg example with new keywords.
• Built docs locally.
• Content of changes should be validated by review.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change (update to the documentation; no code change)
• Breaking change (fix or feature that would cause existing functionality to change)
• Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

• I have read and agree to abide by the Code of Conduct
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• I have added tests to cover my changes.
• I have added myself to the .zenodo.json document.
• I have added my user impacting change to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5580".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[amystamile-usgs]

Not sure if you did this already but a way to test your docs locally is to run ninja docs in your isis environment.

[jrcain-usgs]

Not sure if you did this already but a way to test your docs locally is to run ninja docs in your isis environment.

I didn't know that, thanks! I tried it just now. Luckily no big surprises, but I did catch one typo after seeing it on the page.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5580".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

[github-actions]

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5580".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.