Fix broken links

Contribute/content/how-to-create-github-issues.md

@@ -38,7 +38,7 @@ Of course, if you know how to fix an issue, we invite you to [make the changes y
 
     The more detail you can provide, the more helpful the issue. Tell us what information you sought. Tell us the search terms you used. If you can't get started, tell us how you want to start exploring unfamiliar technology.
 
-That's it! Your issue is now added to the Issues queue. Issues start the conversation about what's needed. The content team will respond to these issues with ideas for what we can add and ask for your opinions. When we create a draft, we'll ask you to [review the PR](#review-open-prs).
+That's it! Your issue is now added to the Issues queue. Issues start the conversation about what's needed. The content team will respond to these issues with ideas for what we can add and ask for your opinions. When we create a draft, we'll ask you to review the PR.
 
 ## Comment on an issue
 

Contribute/content/how-to-review-pull-request.md

@@ -5,7 +5,7 @@ author: carlyrevier
 ms.author: cahublou
 ms.date: 08/28/2023
 ms.topic: contributor-guide
-ms.service: learn
+ms.prod: non-product-specific
 ms.custom: external-contributor-guide
 ---
 
@@ -68,7 +68,7 @@ With PR comments and reviews, you can:
 
         To suggest changes to text that includes a triple-ticked code fence (```), replace the outer/enclosing `suggestion` backticks with tildes (`~~~`).
 
-    1. Edit the text. Use the buttons in the comment box for simple formatting like bold, italics, and bullets, or use the [Markdown syntax elements](/help/contribute/markdown-reference) directly. You can also add comments to this box below the code-block section.
+    1. Edit the text. Use the buttons in the comment box for simple formatting like bold, italics, and bullets, or use the [Markdown syntax elements](markdown-reference.md) directly. You can also add comments to this box below the code-block section.
 
 1. After you've made your comment, select **Start a review**. The PR author will be notified of your changes. If you used the **Insert a suggestion** button in the previous step, the author will be able to commit your suggestion directly to the document.
 

Contribute/content/style-quick-start.md

@@ -46,9 +46,9 @@ Our technical articles are translated into several languages, and some are modif
 
 ## Localized documentation
 
-- If you are contributing to localized documentation, refer to the [Microsoft Language Portal](https://www.microsoft.com/Language/Default.aspx).
-- For localization guidelines, information on language style and usage in technical publications, and information on market-specific data formats, download the [style guide](https://www.microsoft.com/Language/StyleGuides) in your language.
-- For Microsoft localized terminology, search for [product-specific approved terminology](https://www.microsoft.com/Language/Default.aspx) or download the [Microsoft Terminology Collection](https://www.microsoft.com/language/Terminology) in your language.
+- If you are contributing to localized documentation, refer to the [globalization references](https://learn.microsoft.com/globalization/reference/).
+- For localization guidelines, information on language style and usage in technical publications, and information on market-specific data formats, download the [style guide](https://learn.microsoft.com/globalization/reference/microsoft-style-guides) in your language.
+- Visit [Microsoft Terminology](https://learn.microsoft.com/globalization/reference/microsoft-terminology) to search for product-specific approved terminology or to download the Microsoft Terminology Collection in your language.
 - To learn more about localization, see "Global communications" in the [Microsoft Writing Style Guide](/style-guide/global-communications).
 
 [!INCLUDE [note-docsitelocfeedback](../includes/note-docsitelocfeedback.md)]