Issue 592: Removed old exchange-api pages and updated TLS 1.2 referen…

[joewxboy]

…ce to TLSv1.3

Pull Request Template

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes #592

Type of change

Please delete options that are not relevant.

• This change requires a documentation update

...

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
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• 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]

@naphelps I found older exchange-api pages that referenced TLSv1.2, but they were apparently orphans from a mis-configured publish a year ago. I've deleted those three orphaned pages and updated one reference in the User Management section from 1.2 to 1.3

[joewxboy]

@naphelps I found older exchange-api pages that referenced TLSv1.2, but they were apparently orphans from a mis-configured publish a year ago. I've deleted those three orphaned pages and updated one reference in the User Management section from 1.2 to 1.3

You'll note that the "real" pages live in exchange-api/docs instead of the older pages in exchange-api that I'm deleting with this PR.