Merge pull request #2573 from WilliamAntonRohm/W-cross-platform-2

VS "cross-platform" fixes -- gerunds, capitalization, and formatting -- batch #2 of 3

Author: ktoliver

docs/cross-platform/cross-platform-mobile-development-examples.md

@@ -13,7 +13,7 @@ manager: douge
 ms.workload: 
   - "xplat-cplusplus"
 ---
-# Cross-Platform Mobile Development Examples
+# Cross-platform mobile development examples
 Several of the templates installed by Visual C++ for Cross-Platform Mobile Development generate complete examples that you can use to learn from. Additionally, the Windows Dev Center has several example applications that you can download and try out in Visual Studio.  
 
 -   [hello-jni Android Application Sample](https://code.msdn.microsoft.com/hello-jni-Android-790ab73d)  
@@ -46,4 +46,4 @@ Several of the templates installed by Visual C++ for Cross-Platform Mobile Devel
 
  To open one of the examples in Visual Studio, download the zip file and open the **Properties** page of the downloaded file in Explorer. Choose the **Unblock** button then choose **OK**. Extract the contents of the zip file to a convenient location, then open the C++ folder in the extracted sample and open the solution file.  
 
- To build the sample, press F7, or on the menu bar, choose **Build**, **Build Solution**.
+ To build the sample, press **F7**, or on the menu bar, choose **Build**, **Build Solution**.

docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md

@@ -11,7 +11,7 @@ manager: crdun
 ms.workload:
   - "multiple"
 ---
-# Cross-Platform mobile development in Visual Studio
+# Cross-platform mobile development in Visual Studio
 
 You can build apps for Android, iOS, and Windows devices by using Visual Studio.  As you design your app, use tools in Visual Studio to easily add connected services such as Office 365, Azure App Service, and Application Insights.
 
@@ -158,6 +158,6 @@ With Visual Studio Tools for Xamarin, you can target Android, iOS, and Windows i
 
 ## See Also
 
-- [Add Office 365 API's to a Visual Studio project](http://msdn.microsoft.com/library/office/dn605899\(v=office.15\).aspx)
+- [Add Office 365 APIs to a Visual Studio project](http://msdn.microsoft.com/library/office/dn605899\(v=office.15\).aspx)
 - [Azure App Services - Mobile Apps](https://azure.microsoft.com/services/app-service/mobile/)
 - [Visual Studio App Center](https://docs.microsoft.com/appcenter)

docs/cross-platform/cross-platform-prop-pages.md

@@ -11,13 +11,13 @@ manager: douge
 ms.workload: 
   - "xplat-cplusplus"
 ---
-# C++ Cross Platform Property Page Reference
+# C++ cross-platform property page reference
 
 This section contains information about project properties in C++ cross-platform projects.
 
-- [General Project Properties (Android C++)](general-android-prop-page.md)
-- [Android Debugger Properties](android-debugger-prop-page.md)
-- [Clang Project Properties (Android C++)](clang-android-prop-page.md)
-- [General Project Properties (Android C++ Makefile)](general-makefile-android-prop-page.md)
-- [Clang Linker Properties (Android C++)](clanglink-prop-page.md)
-- [NMake Properties (Android C++)](nmake-android-prop-page.md)
+- [General project properties (Android C++)](general-android-prop-page.md)
+- [Android debugger properties](android-debugger-prop-page.md)
+- [Clang project properties (Android C++)](clang-android-prop-page.md)
+- [General project properties (Android C++ Makefile)](general-makefile-android-prop-page.md)
+- [Clang linker properties (Android C++)](clanglink-prop-page.md)
+- [NMake properties (Android C++)](nmake-android-prop-page.md)

docs/cross-platform/customize-project-files-created-by-vstu.md

@@ -11,7 +11,7 @@ manager: crdun
 ms.workload:
   - "unity"
 ---
-# Customize Project Files Created by VSTU
+# Customize project files created by VSTU
 Visual Studio Tools for Unity provides a Unity-style callback during project file generation. Register with the `VisualStudioIntegration.ProjectFileGeneration` event to modify the project file whenever it's regenerated.
 
 ## Demonstrates
@@ -61,5 +61,5 @@ public class ProjectFileHook
 }
 ```
 
-## See Also
- [Example: Log Callback](../cross-platform/share-the-unity-log-callback-with-vstu.md)
+## See also
+ [Example: Log callback](../cross-platform/share-the-unity-log-callback-with-vstu.md)

docs/cross-platform/develop-apps-for-the-universal-windows-platform-uwp.md

@@ -48,4 +48,4 @@ If you have existing Windows Store 8.1 apps, Windows Phone 8.1 apps, or Universa
 After you create your Universal Windows app, you must package your app to install it on a Windows 10 device or submit it to the Windows Store. See [Packaging apps](/windows/uwp/packaging/index).
 
 ## See also
-[Cross-Platform Mobile Development in Visual Studio](../cross-platform/cross-platform-mobile-development-in-visual-studio.md)
+[Cross-platform mobile development in Visual Studio](../cross-platform/cross-platform-mobile-development-in-visual-studio.md)

docs/cross-platform/general-android-prop-page.md

@@ -31,11 +31,11 @@ Property | Description | Choices
 Output Directory | Specifies a relative path to the output file directory; can include environment variables.
 Intermediate Directory | Specifies a relative path to the intermediate file directory; can include environment variables.
 Target Name | Specifies a file name that this project will generate.
-Target Extension | Specifies a file extension that this project will generate. (Example: .exe or .dll)
+Target Extension | Specifies a file extension that this project will generate. (Example: *.exe* or *.dll*)
 Extensions to Delete on Clean | Semi-colon delimited wildcard specification for which files in the intermediate directory to delete on clean or rebuild.
 Build Log File | Specifies the build log file to write to when build logging is enabled.
 Platform Toolset | Specifies the toolset used for building the current configuration; If not set, the default toolset is used
-Configuration Type | Specifies the type of output this configuration generates. | **Dynamic Library (.so)** - Dynamic Library (.so)<br>**Static library (.a)** - Static Library (.a)<br>**Utility** - Utility<br>**Makefile** - Makefile<br>
+Configuration Type | Specifies the type of output this configuration generates. | **Dynamic Library (.so)** - Dynamic Library (*.so*)<br>**Static library (.a)** - Static Library (*.a*)<br>**Utility** - Utility<br>**Makefile** - Makefile<br>
 Target API Level | Android NDK API Level targeted by this configuration.
 Use of STL | Specifies which C++ Standard Library to use for this configuration. | **Minimal C++ runtime library (system)**<br>**C++ runtime static library (gabi++_static)**<br>**C++ runtime shared library (gabi++_shared)**<br>**STLport runtime static library (stlport_static)**<br>**STLport runtime shared library (stlport_shared)**<br>**GNU STL static library (gnustl_static)**<br>**GNU STL shared library (gnustl_shared)**<br>**LLVM libc++ static library (c++_static)**<br>**LLVM libc++ shared library (c++_shared)**<br>
 Thumb Mode | Generate code that executes for thumb microarchitecture. This is applicable for arm architecture only. | **Thumb**<br>**Arm**<br>**Disabled**<br>

docs/cross-platform/general-makefile-android-prop-page.md

@@ -17,11 +17,11 @@ ms.workload:
   - "xplat-cplusplus"
 ---
 
-# General Project Properties (Android C++ Makefile)
+# General project properties (Android C++ Makefile)
 
 Property | Description | Choices
 --- | ---| ---
 Output Directory | Specifies a relative path to the output file directory; can include environment variables.
 Intermediate Directory | Specifies a relative path to the intermediate file directory; can include environment variables.
 Build Log File | Specifies the build log file to write to when build logging is enabled.
-Configuration Type | Specifies the type of output this configuration generates. | **Dynamic Library (.so)** - Dynamic Library (.so)<br>**Static library (.a)** - Static Library (.a)<br>**Utility** - Utility<br>**Makefile** - Makefile<br>
+Configuration Type | Specifies the type of output this configuration generates. | **Dynamic Library (.so)** - Dynamic Library (*.so*)<br>**Static library (.a)** - Static Library (*.a*)<br>**Utility** - Utility<br>**Makefile** - Makefile<br>

docs/cross-platform/getting-started-with-visual-studio-tools-for-unity.md

@@ -11,11 +11,11 @@ manager: crdun
 ms.workload:
   - "unity"
 ---
-# Getting Started with Visual Studio Tools for Unity
+# Get started with Visual Studio Tools for Unity
 
 ## Install Visual Studio
 
-### Unity Bundled Installation
+### Unity bundled installation
 
 Starting with Unity 2018.1, Visual Studio is the default C# script editor for Unity, and is included in the Unity Download Assistant, as well as the Unity Hub installation tool.
 
@@ -35,9 +35,9 @@ During installation, ensure that Visual Studio is checked in the list of compone
 
 The version of Visual Studio included with your Unity installation may not be the latest. It is recommended to check for updates to ensure you have access to the latest tools and features.
 
-- [Updating Visual Studio](../install/update-visual-studio.md)
+- [Update Visual Studio](../install/update-visual-studio.md)
 
-### Manual Installation
+### Manual installation
 
 If you already have Visual Studio 2017 installed, or prefer to manually install, run the Visual Studio installer.
 
@@ -71,7 +71,7 @@ Starting with Unity 2018.1, Visual Studio should be the default external script
 
 1. Once Visual Studio is selected in the **External Script Editor** list, confirm that the **Editor Attaching** checkbox is selected.
 
-1. Close the Preferences dialog to complete the configuration process.
+1. Close the **Preferences** dialog to complete the configuration process.
 
 ## Support for older versions
 
@@ -87,4 +87,4 @@ Starting with Unity 2018.1, Visual Studio should be the default external script
 
 ## Next steps
 
- To learn how to work with and debug your Unity project in Visual Studio, see [Using Visual Studio Tools for Unity](../cross-platform/using-visual-studio-tools-for-unity.md).
+ To learn how to work with and debug your Unity project in Visual Studio, see [Visual Studio Tools for Unity](../cross-platform/using-visual-studio-tools-for-unity.md).

docs/cross-platform/import-an-xcode-project.md

@@ -14,16 +14,16 @@ ms.workload:
 # Import an XCode Project
 Microsoft Visual C++ for Cross-Platform Mobile Development includes support for moving your XCode projects into Visual Studio, where you can create cross-platform libraries and share code with other projects. The Import from XCode wizard simplifies the process of importing projects and splitting out the C++ code in your XCode targets for use as a static library or shared code project. You can manage your iOS-specific code in Visual Studio and still use XCode to do storyboards and builds. For information on how to easily move code back and forth between Visual Studio and XCode, see Move Changes Between XCode and Visual Studio.  
 
-## Using the Import From XCode wizard  
- This topic shows you how to move an XCode project into Visual Studio to take advantage of code sharing and cross-platform solutions. As a prerequisite, you must pair your Mac to Visual Studio to be able to import, export, and build your project. For instructions on how to set up pairing, see [Install And Configure Tools to Build using iOS](../cross-platform/install-and-configure-tools-to-build-using-ios.md). You must also share your XCode project over the network or move it to your Visual Studio computer to use the Import from XCode wizard.  
+## Use the Import From XCode wizard  
+ This topic shows you how to move an XCode project into Visual Studio to take advantage of code sharing and cross-platform solutions. As a prerequisite, you must pair your Mac to Visual Studio to be able to import, export, and build your project. For instructions on how to set up pairing, see [Install and configure tools to build using iOS](../cross-platform/install-and-configure-tools-to-build-using-ios.md). You must also share your XCode project over the network or move it to your Visual Studio computer to use the Import from XCode wizard.  
 
 #### Import from XCode  
 
 1.  On the **File** menu, choose **New**, **Import**, **Import from XCode**. This starts the **Import from XCode** wizard dialog.  
 
      ![Choose the XCode target project to import](../cross-platform/media/cppmdd_u2_importxcode_choose.PNG "CPPMDD_U2_ImportXCode_Choose")  
 
-2.  In the **Choose a project** pane, choose the Browse button to select an XCode .pbxproj file. Navigate to the project file in the **Select XCode project file** dialog, and then choose **Open**.  
+2.  In the **Choose a project** pane, choose the Browse button to select an XCode *.pbxproj* file. Navigate to the project file in the **Select XCode project file** dialog, and then choose **Open**.  
 
      ![Select a project file in the Select Xcode project file dialog](../cross-platform/media/cppmdd_u2_importxcode_browse.PNG "CPPMDD_U2_ImportXCode_Browse")  
 
@@ -53,20 +53,20 @@ Microsoft Visual C++ for Cross-Platform Mobile Development includes support for
 
      Choose **Next** to continue.  
 
-6.  The **Frameworks** pane is used to configure the paths used by Visual Studio for browsing and IntelliSense for your project. The paths must be accessible to Visual Studio for each framework referenced by your XCode project. The wizard checks the framework references in the XCode projects and displays whether Visual Studio can find the framework. Any path you have already set up in the Global Properties should be discovered by Visual Studio. The exceptions are listed in the Frameworks list. For each framework listed with an X, provide a PC accessible path for Visual Studio to find the framework. You can use the browse button [...] to use a **Select Folder** dialog to find the path. The framework path can be either to a local copy, or to a network-accessible share on your Mac.  
+6.  The **Frameworks** pane is used to configure the paths used by Visual Studio for browsing and IntelliSense for your project. The paths must be accessible to Visual Studio for each framework referenced by your XCode project. The wizard checks the framework references in the XCode projects and displays whether Visual Studio can find the framework. Any path you have already set up in the Global Properties should be discovered by Visual Studio. The exceptions are listed in the Frameworks list. For each framework listed with an X, provide a PC accessible path for Visual Studio to find the framework. You can use the browse button **...** to use a **Select Folder** dialog to find the path. The framework path can be either to a local copy, or to a network-accessible share on your Mac.  
 
      ![Import from XCode Frameworks pane](../cross-platform/media/cppmdd_u2_importxcode_frameworks.jpg "CPPMDD_U2_ImportXCode_Frameworks")  
 
      Choose **Next** to continue.  
 
 7.  The **Project Settings** pane allows you to change the framework and include header search path settings for each project the wizard creates. Use this pane to set project-specific paths that differ from the global settings.  
 
-     To set a path for a specific project, In the **Destination project** drop-down, select the project file, then set the values in the **Framework Search Path** and **Include Header Search Path** controls. You can use the browse button [...] next to each control to use a **Select Folder** dialog to find the path.  
+     To set a path for a specific project, In the **Destination project** drop-down, select the project file, then set the values in the **Framework Search Path** and **Include Header Search Path** controls. You can use the browse button **...** next to each control to use a **Select Folder** dialog to find the path.  
 
      ![Import from XCode Projects pane](../cross-platform/media/cppmdd_u2_importxcode_projects.jpg "CPPMDD_U2_ImportXCode_Projects")  
 
-     If no remote Mac has been paired with this PC in Visual Studio, the Configure a Remote Machine link is shown. For instructions on how to set up pairing, see [Install And Configure Tools to Build using iOS](../cross-platform/install-and-configure-tools-to-build-using-ios.md).  
+     If no remote Mac has been paired with this PC in Visual Studio, the **Configure a Remote Machine** link is shown. For instructions on how to set up pairing, see [Install and configure tools to build using iOS](../cross-platform/install-and-configure-tools-to-build-using-ios.md).  
 
      To import the XCode project by using the wizard settings, choose **Import**.  
 
- The Import from XCode wizard creates projects in Visual Studio that correspond to the selected XCode project targets. The code that can be shared with other C++ projects is split into separate Shared Code and static library projects. The remaining code is placed in iOS library and application projects that can be built remotely by Visual Studio. For more information about moving code between Visual Studio and XCode, see [Sync Changes Between XCode and Visual Studio](../cross-platform/sync-changes-between-xcode-and-visual-studio.md).
+ The Import from XCode wizard creates projects in Visual Studio that correspond to the selected XCode project targets. The code that can be shared with other C++ projects is split into separate Shared Code and static library projects. The remaining code is placed in iOS library and application projects that can be built remotely by Visual Studio. For more information about moving code between Visual Studio and XCode, see [Sync changes between XCode and Visual Studio](../cross-platform/sync-changes-between-xcode-and-visual-studio.md).