Correcting links from build warnings

Author: Kraig Brockschmidt

docs/debugger/debugger-windows.md

@@ -37,7 +37,7 @@ You can open most debugger windows while you are debugging your program. To see
 |Modules|CTRL+ALT+U|[How to: Use the Modules Window](../debugger/how-to-use-the-modules-window.md)| 
 |GPU Threads|-|[How to: Use the GPU Threads Window](../debugger/how-to-use-the-gpu-threads-window.md)|
 |Tasks|CTR:+SHIFT+D, K|[Using the Tasks Window](../debugger/using-the-tasks-window.md)| 
-|Python Debug Interactive|SHIFT+ALT+I|[Getting Started with PTVS: Interactive Python](..python-interactive-repl-in-visual-studio.md)
+|Python Debug Interactive|SHIFT+ALT+I|[Getting Started with PTVS: Interactive Python](../python/python-interactive-repl-in-visual-studio.md)
 |JavaScript Console|CTRL+ALT+V, C|[QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md)|
 |DOM Explorer|CTRL+ALT+V, D|[Debug layout using DOM Explorer](../debugger/debug-layout-using-dom-explorer.md)|
 |Live Visual Tree|-|[Inspect XAML properties while debugging](../debugger/inspect-xaml-properties-while-debugging.md)|

docs/python/debugging-python-in-visual-studio.md

@@ -142,7 +142,7 @@ By default, the debugger starts your program with the standard Python launcher,
 | Option | Description |
 | --- | --- |
 | Standard Python launcher | Uses debugging code written in portable Python that is compatible with CPython, IronPython, and variants such as Stackless Python. It provides the best experience for debugging pure Python code. When you attach to a running `python.exe` process, this launcher is used. This launcher also provides [mixed-mode debugging](debugging-mixed-mode-c-cpp-python-in-visual-studio.md) for CPython, allowing you to step seamlessly between C/C++ code and Python code. |
-| Web launcher | Starts your default browser on launch and enables debugging of templates. See the [Web template debugging](template-web.md#debugging) section for more information. |
+| Web launcher | Starts your default browser on launch and enables debugging of templates. See the [Web template debugging](python-web-application-project-templates.md#debugging) section for more information. |
 | Django Web launcher | Identical to the Web launcher and shown only for backwards compatibility. |
 | IronPython (.NET) launcher | Uses the .NET debugger, which only works with IronPython but allows for stepping between any .NET language project, including C# and VB. This launcher is used if you attach to a running .NET process that is hosting IronPython. |
 
@@ -168,7 +168,7 @@ The Python Debug Interactive window (**Debug > Windows > Python Debug Interactiv
 
 ![Python Debug Interactive window](media/debugging-interactive.png)
 
-The Debug Interactive window supports special meta-commands in addition to the [standard REPL commands](interactive-repl.md#meta-commands):
+The Debug Interactive window supports special meta-commands in addition to the [standard REPL commands](python-interactive-repl-in-visual-studio.md#meta-commands):
 
 | Command | Arguments | Description |
 | --- | --- | --- |
@@ -191,6 +191,6 @@ The Debug Interactive window supports special meta-commands in addition to the [
 
 Note that the standard debugger windows such as Processes, Threads, and Call Stack are not synchronized with the Debug Interactive window. Changing the active process, thread, or frame in the Debug Interactive window does not affect the other debugger windows. Similarly, changing the active process, thread, or frame in the other debugger windows does not affect the Debug Interactive window.
 
-The Debug Interactive window has its own set of options, which you can access through **Tools > Options > Python Tools > Debug Interactive Window**. Unlike the regular Python Interactive window, which has a separate instance for each Python environment, there is only one Debug Interactive window and it always uses the Python interpreter for the process being debugged. See [Options - Debugging options](options.md#debugging-options).
+The Debug Interactive window has its own set of options, which you can access through **Tools > Options > Python Tools > Debug Interactive Window**. Unlike the regular Python Interactive window, which has a separate instance for each Python environment, there is only one Debug Interactive window and it always uses the Python interpreter for the process being debugged. See [Options - Debugging options](python-support-options-and-settings-in-visual-studio.md#debugging-options).
 
 ![Debug Interactive Window Options](media/debugging-interactive-options.png)

docs/python/debugging-remote-python-code-on-azure.md

@@ -21,7 +21,7 @@ ms.workload:
 
 # Remotely debugging Python code on Azure
 
-[Python support in Visual Studio](installing-python-support-in-visual-studio.md) includes the ability to remotely debugging Python code that's running on Azure App Service. Unlike simple remote debugging, the target computer in this scenario is not directly accessible over TCP, so Visual Studio provides a proxy that exposes the debugger protocol over HTTP. Projects created using the Web template automatically configure this proxy in the generated `web.debug.config` file. Remote debugging is also enabled when you publish a Debug configuration of your project as described on [Publishing to Azure App Service](template-web.md#publishing-to-azure-app-service).
+[Python support in Visual Studio](installing-python-support-in-visual-studio.md) includes the ability to remotely debugging Python code that's running on Azure App Service. Unlike simple remote debugging, the target computer in this scenario is not directly accessible over TCP, so Visual Studio provides a proxy that exposes the debugger protocol over HTTP. Projects created using the Web template automatically configure this proxy in the generated `web.debug.config` file. Remote debugging is also enabled when you publish a Debug configuration of your project as described on [Publishing to Azure App Service](python-web-application-project-templates.md#publishing-to-azure-app-service).
 
 Because Azure remote debugging uses web sockets, sockets must be enabled for your App Service through the [Azure portal](https://portal.azure.com) by going to **Settings > Application settings** and turning **General settings > Web sockets** to **On**, then selecting **Save** to apply the change. (Note that the **Debugging** settings do not apply to debugging Python.)
 

docs/python/editing-python-code-in-visual-studio.md

@@ -23,7 +23,7 @@ ms.workload:
 
 Developers spend much of their time in the code editor, so [Python support in Visual Studio](installing-python-support-in-visual-studio.md) provides functionality to help you be more productive. Features include IntelliSense syntax highlighting, auto-completion, signature help, method overrides, search, and navigation. 
 
-The editor is also integrated with the interactive window in Visual Studio, making it easy to exchange code between the two. See [Tutorial Step 3: Using the interactive REPL window](tutorial-working-with-python-in-visual-studio-step-03-interactive-repl.md) and [Using the interactive window - Send code to interactive command](interactive-repl.md#send-code-to-interactive-command) for details.
+The editor is also integrated with the interactive window in Visual Studio, making it easy to exchange code between the two. See [Tutorial Step 3: Using the interactive REPL window](tutorial-working-with-python-in-visual-studio-step-03-interactive-repl.md) and [Using the interactive window - Send code to interactive command](python-interactive-repl-in-visual-studio.md#send-code-to-interactive-command) for details.
 
 For an introduction to editing Python code, see [Editing Python code](https://mva.microsoft.com/en-US/training-courses/python-tools-for-visual-studio-2017-18121?l=r2iQH5LWE_4605918567) (Microsoft Virtual Academy, 2m30s):
 
@@ -74,7 +74,7 @@ Typing @ starts a decorator and shows potential decorators. Many of these items
 ![Decorator completion](media/code-editing-completion-decorator.png)
 
 > [!Tip]
-> You can configure the behavior of completions through **Tools > Options > Text Editor > Python > Advanced"**. Among these, **Filter list based on search string**: applies filtering of completion suggestions as you type (default is checked), and **Member completion displays intersection of members** shows only completions that are supported by all possible types (default is unchecked). See [Options - completion results](options.md#completion-results).
+> You can configure the behavior of completions through **Tools > Options > Text Editor > Python > Advanced"**. Among these, **Filter list based on search string**: applies filtering of completion suggestions as you type (default is checked), and **Member completion displays intersection of members** shows only completions that are supported by all possible types (default is unchecked). See [Options - completion results](python-support-options-and-settings-in-visual-studio.md#completion-results).
 
 ### Signature help
 
@@ -102,7 +102,7 @@ To customize the colors, go to **Tools > Options > Environment > Fonts and Color
 ![Fonts and Colors options](media/code-editing-customize-colors.png)
 
 > [!Tip]
-> To disable code coloring, go to **Tools > Options > Text Editor > Python > Advanced** and clear **Miscellaneous Options > Color names based on type**. See [Options - Miscellaneous Options](options.md#miscellaneous-options).
+> To disable code coloring, go to **Tools > Options > Text Editor > Python > Advanced** and clear **Miscellaneous Options > Color names based on type**. See [Options - Miscellaneous Options](python-support-options-and-settings-in-visual-studio.md#miscellaneous-options).
 
 ## Code snippets
 

docs/python/managing-python-environments-in-visual-studio.md

@@ -133,7 +133,7 @@ Startup scripts contain code that the interactive window loads and runs automati
 
 1. When you install an environment, Visual Studio creates a folder `Documents\Visual Studio 2017\Python Scripts\<environment>` where &lt;environment&gt' matches the name of the environment. You can easily navigate to the environment-specific folder with the **Explore interactive scripts** command. When you start the interactive window for that environment, it loads and runs whatever `.py` files are found here in alphabetical order.
 
-1. The **Scripts** control in **Tools > Options > Python Tools > Interactive Windows** tab (see [Interactive windows options](options.md#interactive-windows-options)) is intended to specify an additional folder for startup scripts that are loaded and run in all environments. However, this feature doesn't work at present.
+1. The **Scripts** control in **Tools > Options > Python Tools > Interactive Windows** tab (see [Interactive windows options](python-support-options-and-settings-in-visual-studio.md#interactive-windows-options)) is intended to specify an additional folder for startup scripts that are loaded and run in all environments. However, this feature doesn't work at present.
 
 ### Configure tab
 
@@ -168,7 +168,7 @@ In the latter case, because the environment is located in a protected area of th
 
 Selecting **Always elevate when installing or removing packages** prevents the dialog from appearing for the environment in question. To make the dialog appear again, go to **Tools > Options > Python Tools > General** and select the button, **Reset all permanently hidden dialogs**.
 
-In that same options tab, you can also select **Always run pip as administrator** to suppress the dialog for all environments. See [Options - General tab](options.md#general-options).
+In that same options tab, you can also select **Always run pip as administrator** to suppress the dialog for all environments. See [Options - General tab](python-support-options-and-settings-in-visual-studio.md#general-options).
 
 ### IntelliSense tab
 

docs/python/python-django-web-application-project-template.md

@@ -57,7 +57,7 @@ The Django management console is accessed through various commands on the **Proj
 
     ![Console](media/template-django-console-sync-db.png)
 
-- **Collect Static**: executes `manage.py collectstatic --noinput` to copy all the static files to the path specified by `STATIC_ROOT` in your `settings.py`. Note that when [publishing to Microsoft Azure](template-web.md#publishing-to-azure-app-service), static files are automatically collected as part of the publish operation.
+- **Collect Static**: executes `manage.py collectstatic --noinput` to copy all the static files to the path specified by `STATIC_ROOT` in your `settings.py`. Note that when [publishing to Microsoft Azure](python-web-application-project-templates.md#publishing-to-azure-app-service), static files are automatically collected as part of the publish operation.
 
     ![Console](media/template-django-console-collect-static.png)
 

docs/python/python-interactive-repl-in-visual-studio.md

@@ -114,7 +114,7 @@ In addition to working within the interactive window directly, you can select co
 This command is useful for iterative or evolutionary code development, including testing your code as you develop it. For example, once you've sent a piece of code to the interactive window and seen its output, you can press the up arrow to show the code again, modify it, and test it quickly by pressing Ctrl+Enter. (Pressing Enter at the end of input executes it, but pressing Enter in the middle of input inserts a newline.) Once you have the code you want, you can easily copy it back into your project file.
 
 > [!Tip]
-> By default, Visual Studio removes >>> and ... REPL prompts when pasting code from the interactive window into the editor. You can change this behavior on  the **Tools > Options > Text Editor > Python > Advanced** tab using the **Paste removes REPL prompts** option. See [Options - Miscellaneous options](options.md#miscellaneous-options).
+> By default, Visual Studio removes >>> and ... REPL prompts when pasting code from the interactive window into the editor. You can change this behavior on  the **Tools > Options > Text Editor > Python > Advanced** tab using the **Paste removes REPL prompts** option. See [Options - Miscellaneous options](python-support-options-and-settings-in-visual-studio.md#miscellaneous-options).
 
 <!-- After 15.3 is released, you can also press "Undo" after pasting to restore prompts. Press "Undo" a second time to remove the pasted code entirely. -->
 
@@ -128,4 +128,4 @@ Visual Studio also detects code cells starting with comments like `# In[1]:`, wh
 
 The interactive window includes IntelliSense based on the live objects, unlike the code editor in which IntelliSense is based on source code analysis only. These suggestions are more correct in the interactive window, especially with dynamically generated code. The drawback is that functions with side-effects (such as logging messages) may impact your development experience.
 
-If this behavior is a problem, change the settings under **Tools > Options > Python Tools > Interactive Windows** in the **Completion Mode** group, as described on [Options - Interactive Windows options](options.md#interactive-windows-options).
+If this behavior is a problem, change the settings under **Tools > Options > Python Tools > Interactive Windows** in the **Completion Mode** group, as described on [Options - Interactive Windows options](python-support-options-and-settings-in-visual-studio.md#interactive-windows-options).

docs/python/python-support-options-and-settings-in-visual-studio.md

@@ -43,7 +43,7 @@ There are also additional Python-specific options on the **Text Editor > Python
 | Show the Output Window when creating virtual environments| On | Clear to prevent the output window from appearing. |
 | Show the Output Window when installing or removing packages | On |  Clear to prevent the output window from appearing. |
 | Always run pip as administrator | Off | Always elevates `pip install` operations for all environments. When installing packages, Visual Studio prompts for administrator privileges if the environment is located in a protected area of the file system such as `c:\Program Files`. In that prompt you can choose to always elevate `pip install` for just that one environment. See [Python environments - pip tab](managing-python-environments-in-visual-studio.md#pip-tab). |
-| Automatically generate completion DB on first use | On | For [IntelliSense completions](code-editing.md#intellisense) to work for a library, Visual Studio must generate a completion database for that library. Building the database is done in the background when a library is installed, but may not be complete when you start writing code. With this option selected, Visual Studio prioritizes completion of the database for a library when you write code that uses it. |
+| Automatically generate completion DB on first use | On | For [IntelliSense completions](editing-python-code-in-visual-studio.md#intellisense) to work for a library, Visual Studio must generate a completion database for that library. Building the database is done in the background when a library is installed, but may not be complete when you start writing code. With this option selected, Visual Studio prioritizes completion of the database for a library when you write code that uses it. |
 | Ignore system-wide PYTHONPATH variables | On | PYTHONPATH is ignored by default because Visual Studio provides a more direct means to specify search paths in environments and projects. See [Python Environments - search paths](managing-python-environments-in-visual-studio.md#search-paths) for details. |
 | Update search paths when adding linked files | On | When set, adding a [linked file](managing-python-projects-in-visual-studio.md#linked-files) to a project updates [search paths](managing-python-environments-in-visual-studio.md#search-paths) so that IntelliSense can include the contents of the linked file's folder in its completion database. Clear this option to exclude such content from the completion database. |
 | Warn when imported module cannot be found | On | Clear this option to suppress warnings when you know an imported module isn't presently available but doesn't otherwise affect code operation. |

docs/python/quickstart-01-python-in-visual-studio-project-from-existing-code.md

@@ -1,5 +1,5 @@
 ---
-title: Quickstart: Creating a Python project in Visual Studio from existing code | Microsoft Docs
+title: Quickstart - Creating a Python project in Visual Studio from existing code | Microsoft Docs
 description: Get started quickly using Python by creating a Visual Studio project from existing code, using a convenient template.
 ms.custom: ""
 ms.date: 01/08/2018

docs/python/quickstart-02-python-in-visual-studio-project-from-template.md

@@ -1,5 +1,5 @@
 ---
-title: Quickstart: Create a Python project in Visual Studio using a template | Microsoft Docs
+title: Quickstart - Create a Python project in Visual Studio using a template | Microsoft Docs
 description: Get started quickly using Python by creating a Visual Studio project using one of the built-in templates.
 ms.custom: ""
 ms.date: 09/25/2017

docs/python/quickstart-03-python-in-visual-studio-project-from-repository.md

@@ -1,5 +1,5 @@
 ---
-title: Quickstart: Cloning a repository of Python code in Visual Studio | Microsoft Docs
+title: Quickstart - Cloning a repository of Python code in Visual Studio | Microsoft Docs
 description: Get started quickly using Python by cloning the Python koans repository using Visual Studio Team Explorer.
 ms.custom: ""
 ms.date: 09/25/2017

docs/python/quickstart-04-python-in-visual-studio-project-from-cookiecutter.md

@@ -1,5 +1,5 @@
 ---
-title: Quickstart: Create a Python project using Cookiecutter in Visual Studio | Microsoft Docs
+title: Quickstart - Create a Python project using Cookiecutter in Visual Studio | Microsoft Docs
 description: Get started quickly using Python by using a Cookiecutter template in Visual Studio.
 ms.custom: ""
 ms.date: 09/22/2017

docs/python/tutorial-working-with-python-in-visual-studio-step-02-writing-code.md

@@ -76,7 +76,7 @@ Although Solution Explorer is where you manage project files, the *editor* windo
     ```
 
     > [!Tip]
-    > Completions work with substrings as you type, matching parts of words, letters at the beginning of words, and even skipped characters. See [Editing code - Completions](code-editing.md#completions) for details.
+    > Completions work with substrings as you type, matching parts of words, letters at the beginning of words, and even skipped characters. See [Editing code - Completions](editing-python-code-in-visual-studio.md#completions) for details.
 
 1. Add a little more code to print the cosine values for 360 degrees: