Audited examples in endpoint.r, see TODO items for further edits needed.

[tinatownes]

Checklist

Please:

• Make sure this PR is against "dev", not "main" (unless this is a release
  PR).
• Request a review from one of the current epidatr main reviewers:
  brookslogan, dshemetov, nmdefries, dsweber2.
• Makes sure to bump the version number in DESCRIPTION. Always increment
  the patch version number (the third number), unless you are making a
  release PR from dev to main, in which case increment the minor version
  number (the second number).
• Describe changes made in NEWS.md, making sure breaking changes
  (backwards-incompatible changes to the documented interface) are noted.
  Collect the changes under the next release number (e.g. if you are on
  1.7.2, then write your changes under the 1.8 heading).

Change explanations for reviewer

Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch

• Resolves #{issue number}

[nmdefries]

@dshemetov Can you take a look at this?

[dshemetov]

Going to approve this so you can just merge after fixing, but please make sure to address the two minor issues (both URLs) I raised before merging. The CRAN url in particular will make the next release harder if not addressed.