Issue 660 - with help from Bob

[euconnor]

Pull Request Template

Description

This PR fixes part C of issue 660.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• This change requires a documentation update

This change is several documentation updates.

How Has This Been Tested?

I need to figure out how to generate the OH docs in a test environment. No testing done yet.

Additional Context (Please include any Screenshots/gifs if relevant)

N/a

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• [n/a] I have made corresponding changes to the documentation
• [n/a] My changes generate no new warnings
• [n/a] I have added tests that prove my fix is effective or that my feature works
• [n/a] New and existing unit tests pass locally with my changes
• [n/a] Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings
• I have tagged the reviewers in a comment below incase my pull request is ready for a review
• [?] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

[joewxboy]

NOTE: we may want to consider replacing some of the proper nouns with the liquid template reference to the keywords ... if we're still thinking about how this translates, and if it helps downstream.

[dlarson04]

@euconnor - There is a problem with this PR... All the files from docs/anax/docs folder actually come from the docs folder under https://github.com/open-horizon/anax.

They are then copied here

To make changes to those files, that anax repo should be changed

[euconnor]

Thanks for pointing that out @dlarson04. I knew there was some cross-repo copying, but forgot to check the precise details.
Is the quickest solution to copy the changes in this PR into the anax repo, and create a new PR? I think it would work OK, because the last update to a .md file in the docs folder in the anax repo was two months ago.