update paths (#5936)

* update paths

* touch up instructions

Author: TylerMSFT

.github/copilot-instructions.md

@@ -1,6 +1,6 @@
-When writing documentation, follow the following guidelines:
+When writing documentation, follow these guidelines:
 
-- Follow the style of the [Microsoft Writing Style Guide](https://learn.microsoft.com/en-us/style-guide/welcome/).
+- Follow the style of the [Microsoft Writing Style Guide](https://learn.microsoft.com/style-guide/welcome/).
 - Headings should be in sentence case, not title case. Don't use gerunds in titles.
 - Use the active voice whenever possible, and second person to address the reader directly.
 - Use a conversational tone with contractions.
@@ -14,14 +14,14 @@ When writing documentation, follow the following guidelines:
 - Number ordered list items all as "1." instead of "1.", "2.", etc. Use bullets for unordered lists.
 - Use **bold** when referring to UI elements. Use `code style` for file names and folders, custom types, and other text that should never be localized.
 - Put raw URLs within angle brackets.
-- When you are going to refer to another file or an article on the web, use a link. For example, "For more information, see [C++ language reference](../cpp/cpp-language-reference.md)." 
+- When you are going to refer to another file or an article on the web, use this format: "For more information, see [C++ language reference](../cpp/cpp-language-reference.md)." The exception to this is the See Also links at the end of an article. Those should be markdown links and contain the title of the article you link to as the descriptive portion of the link.
 - Include links to related topics and resources where appropriate. Use relative links if the target file lives in this repo. If you add a link to another page on learn.microsoft.com that's not in this repo, remove https://learn.microsoft.com/en-us from the link.
 - If you're adding a new Markdown file, it should be named in all lowercase with hyphens separating words. Also, omit any filler words such as "the" or "a" from the file name.
-- If you're adding a new Markdown file, the following indicates where it should go the folder structure. If you aren't sure, ask. The following folder structure is how it looks on my hard drive. To map to GitHub, for example, C:\Users\twhitney\repos\cpp-docs-pr\docs\linux is docs/linux
-    If the file is about Linux, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\linux folder.
-    If the file is about the C++ Standard Template Library (STL), put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\standard-library folder.
-    If the file is about the C runtime, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\c-runtime-library folder.
-    If the file is about the C++ language, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\cpp folder.
-    If the file is about a C++ feature specific to the Visual Studio IDE, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\ide folder.
-    If the file is about the build process or modules, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\build\reference folder.
-    If the file is about Build Insights, put it in the C:\Users\twhitney\repos\cpp-docs-pr\docs\build-insights folder.
+- If you're adding a new Markdown file, the following indicates where it should go the folder structure. If you aren't sure, ask.
+    If the new file is about Linux, put it in the docs/linux folder.
+    If the new file is about the C++ Standard Template Library (STL), put it in the docs/standard-library folder.
+    If the new file is about the C runtime, put it in the docs/c-runtime-library folder.
+    If the new file is about the C++ language, put it in the docs/cpp folder.
+    If the new file is about a C++ feature specific to the Visual Studio IDE, put it in the docs/ide folder.
+    If the new file is about the build process or modules, put it in the docs/build\reference folder.
+    If the new file is about Build Insights, put it in the docs/build-insights folder.