Fix links in Legacy_Application_Management_Cheat_Sheet.md

[albrektsson]

You're A Rockstar

Thank you for submitting a Pull Request (PR) to the Cheat Sheet Series.

🚩 If your PR is related to grammar/typo mistakes, please double-check the file for other mistakes in order to fix all the issues in the current cheat sheet.

Please make sure that for your contribution:

• All the markdown files do not raise any validation policy violation, see the policy.
• You verified/tested the effectiveness of your contribution (e.g., the defensive code proposed is really an effective remediation? Please verify it works!).
• The CI build of your PR pass, see the build status here.

Thank you again for your contribution 😃

[szh]

Thank you for fixing these! Because of the build process automation, the way we formulate the links is as below:
Essentially the mistake here is the "/" before the cheat sheet name.

Suggested change

**Risk Assessment and Threat Modeling:** Ensure your organization has a clear understanding of the level of risk and the kinds of threats theoretically posed by using the legacy application and its specific components (e.g. specific API routes or open ports on hosting infrastructure). This may be informed by formal or informal threat-modeling of an application, as described in the [Threat Modeling Cheat Sheet](/cheatsheets/Threat_Modeling_Cheat_Sheet.html). Qualifying the risk posed by legacy software might also be aided by using an industry standard risk assessment framework, such as the NIST (National Institute of Standards and Technology) [Risk Management Framework](https://csrc.nist.gov/Projects/risk-management). There are many threat modeling and risk assessment frameworks and tools that have different strengths and weaknesses.

**Risk Assessment and Threat Modeling:** Ensure your organization has a clear understanding of the level of risk and the kinds of threats theoretically posed by using the legacy application and its specific components (e.g. specific API routes or open ports on hosting infrastructure). This may be informed by formal or informal threat-modeling of an application, as described in the [Threat Modeling Cheat Sheet](Threat_Modeling_Cheat_Sheet.md). Qualifying the risk posed by legacy software might also be aided by using an industry standard risk assessment framework, such as the NIST (National Institute of Standards and Technology) [Risk Management Framework](https://csrc.nist.gov/Projects/risk-management). There are many threat modeling and risk assessment frameworks and tools that have different strengths and weaknesses.

[albrektsson]

Sneaky.. take two committed :D

[szh]

LGTM, thank you!

[kwwall]

Given there are already 2 approvals, my appologies for being so late to the party, but instead of:

Inventory Management: Start by compiling documentation identifying ...

wouldn't it be better to word that as:

Inventory Management: Start by gathering documentation identifying ...

since "compiling" has a unique definition to us CS and IT folks and one generally does not "compile documentation" in the traditional CS sense if it's not too late to change that?

[mackowski]

Good point form @kwwall, this change is already merged but if others agree we can create new PR with this small change.