@@ -13,14 +13,14 @@
 # [C/C++ Preprocessor](preprocessor/c-cpp-preprocessor-reference.md)
 # [C Runtime Library](c-runtime-library/c-run-time-library-reference.md)
 # [C++ Standard Library](standard-library/cpp-standard-library-reference.md)
+# [Projects and Build Systems](build/building-c-cpp-programs.md)
 # [Windows Development](windows/overview-of-windows-programming-in-cpp.md)
 # [Linux Development](linux/download-install-and-setup-the-linux-development-workload.md)
 # [Cloud and Web Programming in Visual C++](cloud/cloud-and-web-programming-in-visual-cpp.md)
 # [Parallel Programming](parallel/parallel-programming-in-visual-cpp.md)
 # [Data Access](data/data-access-in-cpp.md)
 # [Text and Strings](text/text-and-strings-in-visual-cpp.md)
 # [vcpkg: A Package Manager for C++](vcpkg.md)
-# [Configure and compile C++ projects](build/building-c-cpp-programs.md)
 # [Port and Upgrade C++ Code](porting/visual-cpp-porting-and-upgrading-guide.md)
 # [Security Best Practices for C++](security/security-best-practices-for-cpp.md)
 ## [Running as a Member of the Users Group](security/running-as-a-member-of-the-users-group.md)
 
@@ -1,12 +1,12 @@
 ---
-title: "Building C/C++ Projects in Visual Studio"
+title: "C/C++ Projects and build systems in Visual Studio"
 ms.description: "Use Visual Studio to compile and build C++ projects for Windows, ARM or Linux based on any project system."
 ms.date: "12/08/2018"
 f1_keywords: ["vcbuilding", "buildingaprogramVC"]
 helpviewer_keywords: ["builds [C++]", "Visual C++ projects, building", "projects [C++], building", "builds [C++], options", "Visual C++, build options"]
 ms.assetid: fa6ed4ff-334a-4d99-b5e2-a1f83d2b3008
 ---
-# Building C/C++ projects in Visual Studio
+# C/C++ Projects and build systems in Visual Studio
 
 You can use Visual Studio 2017 to edit, compile and build any C++ code base with full IntelliSense support without having to convert that code into a Visual Studio project or compile with the MSVC toolset. For example, you can edit a cross-platform CMake project in Visual Studio on a Windows machine, then compile it for Linux using g++ on a remote Linux machine.
 
 
@@ -13,7 +13,7 @@ A *Visual Studio project* is a project based on the MSBuild build system. MSBuil
 
 You can create C++ projects by choosing **File &#124; New &#124; Project**, then choosing Visual C++ in the left pane. In the center pane you see a list of project templates: 
 
-   ![Project Templates](media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
+   ![Project Templates](../media/vs2017-new-project.png "Visual Studio 2017 New Project Dialog")
 
 For more information about all the default project templates that are included in Visual Studio, see [C++ project templates in Visual Studio](reference/visual-cpp-project-types.md). You can create your own project templates. For more information, see [How to: Create project templates](/visualstudio/ide/how-to-create-project-templates).
 
@@ -41,7 +41,7 @@ To compile and run the new project, press **F5** or click the *debug dropdown* w
 
 A new project compiles without errors. When adding your own code, you may occasionally introduce an error or trigger a warning. An error prevents the build from completing; a warning does not. All errors and warnings will appear both in the Output Window and in the Error List when you build the project. 
 
-   ![Output window and error list](media/vs2017-output-error-list.png) "Visual Studio 2017 error List")
+   ![Output window and error list](../media/vs2017-output-error-list.png) "Visual Studio 2017 error List")
 
 In the Error List, you can press **F1** on a highlighted error to go to its documentation topic.
 
 
@@ -13,7 +13,7 @@ The CL tool uses the following environment variables:
 
 - INCLUDE, which must point to the \include subdirectory of your Visual C++ installation.
 
-- LIBPATH, which specifies directories to search for metadata files referenced with [#using](../preprocessor/hash-using-directive-cpp.md). See `#using` for more information on LIBPATH.
+- LIBPATH, which specifies directories to search for metadata files referenced with [#using](../../preprocessor/hash-using-directive-cpp.md). See `#using` for more information on LIBPATH.
 
 You can set the CL or \_CL\_ environment variable using the following syntax:
 
@@ -26,7 +26,7 @@ You can use these environment variables to define the files and options you use
 
 You cannot use the /D option to define a symbol that uses an equal sign (=). You can substitute the number sign (#) for an equal sign. In this way, you can use the CL or \_CL\_ environment variables to define preprocessor constants with explicit values—for example, `/DDEBUG#1` to define `DEBUG=1`.
 
-For related information, see [Set Environment Variables](../build/setting-the-path-and-environment-variables-for-command-line-builds.md).
+For related information, see [Set Environment Variables](../setting-the-path-and-environment-variables-for-command-line-builds.md).
 
 ## Examples
 
 
@@ -231,7 +231,7 @@ These notes apply to the preceding list:
 
 ## See Also
 
-[File Types Created for Visual C++ Projects](../file-types-created-for-visual-cpp-projects.md)<br>
+[File Types Created for Visual C++ Projects](file-types-created-for-visual-cpp-projects.md)<br>
 [#define Directive (C/C++)](../../preprocessor/hash-define-directive-c-cpp.md)<br>
 [#undef Directive (C/C++)](../../preprocessor/hash-undef-directive-c-cpp.md)<br>
 [SAL Annotations](../../c-runtime-library/sal-annotations.md)<br>