1929 update markdown link

[Arminta-Jenkins-NIST]

Committer Notes

Updates links in the src/specifications/profile-resolution/readme.md. Closes #1926.

All Submissions:

• Have you selected the correct base branch per Contributing guidance?
• Have you set "Allow edits and access to secrets by maintainers"?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?
• Have you squashed any non-relevant commits and commit messages? [instructions]
• Do all automated CI/CD checks pass? (Will follow up see Scheduled Check of Markdown Documents Found Bad Hyperlinks #1926 (comment) for unrelated issue but still from link checking.)

By submitting a pull request, you are agreeing to provide this contribution under the CC0 1.0 Universal public domain dedication.

(For reviewers: The wiki has guidance on code review and overall issue review for completeness.)

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you included examples of how to use your new feature(s)?
• Have you updated all OSCAL website and readme documentation affected by the changes you made? Changes to the OSCAL website can be made in the docs/content directory of your branch.

[aj-stein-nist]

Looks good to me, thanks for taking care of this.

[aj-stein-nist]

@Arminta-Jenkins-NIST, I can tell the xmllint.net failure is an ephemeral one in this failed build, but as a learning experience, can you go to the failed build and click re-run job to test that? This transient error has happened with this domain in the past. If it does not go green this time, I will merge anyway (it happens every few months), but you corrected what you need. I will just note it in the checklist. Thanks.

[wendellpiez]

LGTM

[aj-stein-nist]

@Arminta-Jenkins-NIST, I can tell the xmllint.net failure is an ephemeral one in this failed build, but as a learning experience, can you go to the failed build and click re-run job to test that? This transient error has happened with this domain in the past. If it does not go green this time, I will merge anyway (it happens every few months), but you corrected what you need. I will just note it in the checklist. Thanks.

If you hadn't done it yet, Arminta, you can disregard. An updated link checker pass this evening confirms there is some issue with the GH infrastructure and xmllint.net and the linux.die.net manual page mirror sites too (ironically enough): #1926 (comment). I will merge this now to stop some of the issues and open a new issue to suppress checks for those domains tomorrow if it keeps happening.