fixing copy edits

timeyoutakeit · timeyoutakeit · commit 41d88f191cf1 · 2017-05-10T13:43:36.000-04:00
diff --git a/mac/create-and-edit-configurations.md b/mac/create-and-edit-configurations.md
@@ -8,27 +8,31 @@ ms.topic: article
 ms.assetid: CC1B72D6-12FF-4CCC-A9D4-00F2DC14589F
 ---
 
-# Creating and Editing Build Configurations
+# Creating and editing build configurations
 
-Build Configurations can be create for individual projects or on a solution wide basis. These configurations will give you precise control over your build.
+Build configurations can be created for individual projects or on a solution-wide basis. These configurations will give you precise control over a build.
 
 The options menu for both projects and solutions provide you with an area to create and edit new and existing configurations.
 
-## Creating a Project Build Configurations
+## Creating a project build configurations
+
+To create a project build configuration, take the following steps:
 
 1. Right-click on the project node and select **Options**.
 
 2. In the Project Options dialog, select **Build > Configurations**:
 
     ![Configurations manager in project options](media/create-and-edit-configurations-image2.png)
 
-3. To create a new configuration select **Add**. Alternatively, you can copy one of the existing configurations.
+3. To create a new configuration, select **Add**. Alternatively, you can copy one of the existing configurations.
 
 Once the configuration has been created, you can use the **Build** section in the Project Options to adapt properties appropriate to your configuration:
 
 ![Configure build options](media/create-and-edit-configurations-image3.png)
 
-## Creating a Solutions Build Configurations
+## Creating a solution build configuration
+
+To create a solution build configuration, take the following steps:
 
 
 1. Right-click on the Solution node and select **Options**.
@@ -37,13 +41,13 @@ Once the configuration has been created, you can use the **Build** section in th
     
     ![Configurations manager in solution options](media/create-and-edit-configurations-image1.png)
 
-3. To create a new configuration select **Add**. Alternatively, you can copy one of the existing configurations.
+3. To create a new configuration, select **Add**. Alternatively, you can copy one of the existing configurations.
 
 Once the configuration has been created, you can use the **Build** section in each project's options to adapt properties appropriate to your configuration:
 
 ![Configure build options](media/create-and-edit-configurations-image3.png) 
 
-## Editing a Build Configuration
+## Editing a build configuration
 
 To rename a configuration, select it from the Configuration list in the Project or Solution Options:
 
diff --git a/mac/report-a-problem.md b/mac/report-a-problem.md
@@ -7,7 +7,7 @@ ms.topic: article
 ms.assetid: 1C7AC52E-754E-473F-A5B5-00C3A40DAACD
 ---
 
-# How to Report a Problem in Visual Studio for Mac
+# How to report a problem in Visual Studio for Mac
 
 If you encounter a problem with Visual Studio for Mac, we want to know about it so that we can diagnose and fix it. 
 
@@ -17,7 +17,7 @@ To report a problem with Visual Studio for Mac, use the **Report a Problem** lin
 
 ![report a problem link](media/report-problem-image1.png)
 
-This displays the **Report a Problem** web page. You can use this page to view all existing problems, vote on similar problems, and submit solutions to other peoples problems:
+This displays the **Report a Problem** web page. You can use this page to view all existing problems, vote on similar problems, and submit solutions to problems reported by other people:
 
 ![report a problem webpage](media/report-problem-image2.png)
 
@@ -27,10 +27,10 @@ If you haven't already logged in to the Developer Community application, you'll
 
 ![report a problem webpage](media/report-problem-image3.png)
 
-Give a descriptive title for the issue along with any additional information about that issue that you feel may be useful. When possible, please provide us with reproduction steps as this allows us to understand and fix your issue as quickly as possible.
+Give a descriptive title for the issue along with any additional information about that issue that you feel might be useful. When possible, please provide us with reproduction steps as this allows us to understand and fix your issue as quickly as possible.
 
 ![report a problem webpage](media/report-problem-image4.png)
 
-## Provide a Suggestion
+## Provide a suggestion
 
 Use the **Provide a Suggestion** link on the welcome page to direct you to Visual Studio for Mac's UserVoice page. From here you can add new requests or vote on existing requests.
diff --git a/mac/set-up-git-repository.md b/mac/set-up-git-repository.md
@@ -8,13 +8,13 @@ ms.topic: article
 ms.assetid: E992FA1D-B2AD-4A28-ADC6-47E4FC471060
 ---
 
-# Setting Up a Git Repository
+# Setting up a Git repository
 
 Git is a distributed version control system that allows teams to work on the same documents simultaneously. This means that there is a single server that contains all the files, but whenever a repository is checked out from this central source, the entire repository is cloned locally to your machine.
 
 There are many remote hosts that allow you to work with Git for version control, however the most common of these is GitHub. The example below uses a GitHub host, but you can use any Git host for version control in Visual Studio for Mac.
 
-If you wish to use GitHub, ensure that you have your account created and configured before following the steps below. 
+If you wish to use GitHub, ensure that you have an account created and configured before following the steps below. 
 
 To set up a Git repository, execute the following steps:
 
@@ -41,11 +41,11 @@ To set up a Git repository, execute the following steps:
 
     ![](media/version-control-git5.png)
 
-7. Enter the name of the repository as you would like it to display locally, and paste in the URL from step #3. Your Repository Configuration dialog should look similar to the following, press OK: 
+7. Enter the name of the repository as you would like it to display locally, and paste in the URL from step #3. Your Repository Configuration dialog should look similar to the following. Press OK: 
 
     ![Enter git details dialog](media/version-control-git6.png)
 
-    Note that it is also possible to use SSH to connect to git.
+    Note that it is also possible to use SSH to connect to Git.
 
 8. To attempt to publish the app to Git, select the repository just created,  and ensure that both **Module Name** and **Message** text fields are completed:
 
diff --git a/mac/set-up-subversion-repository.md b/mac/set-up-subversion-repository.md
@@ -8,15 +8,15 @@ ms.topic: article
 ms.assetid: 0D58FB37-530E-495B-BED6-FD499477A9B6
 ---
 
-# Setting Up a Subversion Repository
+# Setting up a Subversion repository
 
-Subversion is a centralized version control system. This means that there is a single server that contains all files and revisions from which users can check out any version of any file. When files are checked out from a remote Subversion repository, the user will get a snapshot of the repository at that particular point in time.
+Subversion is a centralized version control system. This means that there is a single server that contains all files and revisions from which users can check out any version of any file. When files are checked out from a remote Subversion repository, the user will get a snapshot of the repository at that point in time.
 
-Before starting to use Subversion,  the Xcode command line tools must be installed, which includes the correct svn packages. You can check that SVN is installed in Terminal with the following command:
+Before starting to use Subversion, the Xcode command line tools must be installed as they include the correct svn packages. You can check that SVN is installed in Terminal with the following command:
 
 `svn h`
 
-1. Create a free SVN repository online. For this example [Assembla](https://app.assembla.com/) was used. Once created, a URL will be provided, which will be used to connect to the repository: 
+1. Create a free SVN repository online. For this example, [Assembla](https://app.assembla.com/) was used. Once created, a URL will be provided, which will be used to connect to the repository: 
 
     ![Obtain SVN URL and copy it](media/version-control-subversion1-sml.png)
 
@@ -38,5 +38,5 @@ Before starting to use Subversion,  the Xcode command line tools must be install
 
     ![](media/version-control-subversion5.png)
 
-8.	All of the version control commands available should now be visible in the version control menu.
+8.	All the version control commands available should now be visible in the version control menu.
 
diff --git a/mac/troubleshooting.md b/mac/troubleshooting.md
@@ -10,19 +10,19 @@ ms.assetid: CE860D79-E29E-4B93-B094-BE74B35FC1C2
 
 # Troubleshooting
 
-## Viewing Logs in Visual Studio for Mac
+## Viewing logs in Visual Studio for Mac
  
 Logs can be found by browsing to the **Help > Open Log Directory** menu item, as illustrated below:
 
 ![Open Log directory menu item](media/troubleshooting-image1.png)
 
-## Viewing Exceptions
+## Viewing exceptions
 
 When an exception has been caught, an exception bubble will appear. To view more details, select the **View Details** button:
 
 ![View more details about an exception](media/troubleshooting-image2.png)
 
-This will the display Show Details dialog, providing more information regarding the exception:
+This will display the **Show Details** dialog, providing more information regarding the exception:
 
 ![](media/troubleshooting-image3.png)
 
@@ -37,7 +37,7 @@ Important sections of the dialog, which are numbered above are described in deta
 7. Example of user code entries.
 8. Properties view, which shows all properties and fields of the exception. This can be collapsed via a disclosure arrow.
 9. Inner exception tree view. Select inner exceptions in this view via keyboard up/down arrows or with the mouse or trackpad.
-10. By default, this is set to what the **Debug project code only** option in debugger settings is set. Selecting this box will enable all non-user code to collapse into one line in the stacktrace.
+10. By default, this is set to what the **Debug project code only** option in debugger settings is set to. Selecting this box will enable all non-user code to collapse into one line in the stacktrace.
 11. A copy button to copy the `exception.ToString()` output to clipboard.
 
 Note that some of these sections will only be visible when exception has an inner exception.
diff --git a/mac/version-control.md b/mac/version-control.md
@@ -8,21 +8,21 @@ ms.topic: article
 ms.assetid: 49917483-28AA-4598-A847-71F1F2E0DCB5
 ---
 
-# Version Control
+# Version control
 
-Version control is a system of managing files over many different versions, and – in software development – is generally contributed to by many developers. The principal purpose of any version control system (_VCS_) is to find a solution that enables all users to work on the codebase at the same time.
+Version control is a system for managing files over many different versions, and – in software development – is generally contributed to by many developers. The principal purpose of any version control system (_VCS_) is to find a solution that enables all users to work on the codebase at the same time.
 
 At the core of any version control system is a _repository_, which acts as the central data store for all the different files – similar to a file server. However, unlike a file server, the repository contains the entire history of the project and all revisions that have been made.
 
-If the repository is the central data store, it is logical for each user to have a local store of the data, allowing them to work on it. This is called a _working copy_. In Visual Studio for Mac your working copy will appear just as any other local directory on your machine, allowing you to read and write from any of the files. However, because Visual Studio for Mac has Version control system integration, you can leverage the power of Subversion and Git without leaving the IDE.
+If the repository is the central data store, it is logical for each user to have a local store of the data, allowing them to work on it. This is called a _working copy_. In Visual Studio for Mac your working copy will appear just as any other local directory on your machine, allowing you to read from and write to any of the files. However, because Visual Studio for Mac has Version control system integration, you can leverage the power of Subversion and Git without leaving the IDE.
 
-Subversion is a centralized version control system. This means that there is a single server that contains all files and revisions from which users can check out any version of any file. When files are checked out from a remote Subversion repository, the user will get a snapshot of the repository at that particular point in time.
+Subversion is a centralized version control system. This means that there is a single server that contains all files and revisions from which users can check out any version of any file. When files are checked out from a remote Subversion repository, the user will get a snapshot of the repository at that point in time.
 
 Git is a distributed version control system that allows teams to work on the same documents simultaneously. This means that there might a single server that contains all the files, but whenever a repository is checked out from this central source, the entire repository is cloned locally to your machine.
 
 # Basic Concepts 
 
-Visual Studio for Mac provides support for both Git and Subversion version control systems. The guides linked below explore setting up Git and Subversion repositories through Visual Studio for Mac, and also simple functionality such as reviewing, committing, and pushing changes.
+Visual Studio for Mac provides support for both Git and Subversion version control systems. The guides linked below explore setting up Git and Subversion repositories through Visual Studio for Mac, as well as simple functionality such as reviewing, committing, and pushing changes.
 
 * [Setting Up a Git Repository](~/set-up-git-repository.md) 
 * [Working with Git](~/working-with-git.md)
diff --git a/mac/working-with-git.md b/mac/working-with-git.md
@@ -24,7 +24,7 @@ The image below illustrates the options provided by Visual Studio for Mac by the
 
 Pushing and Pulling are two of the most commonly used actions within Git. To synchronize changes that other people have made to the remote repository, you must **Pull** from there. This is done in Visual Studio for Mac by selecting **Version Control > Update Solution**.
 
-Once you have updated your files, reviewed and committed them, you then have to **Push** them to the remote repository to allow others to access your changes. This is done in Visual Studio for Mac by selecting **Version Control > Push Changes**. This will display the Push dialog, allowing you to view the committed changes, and select the branch to push to:
+Once you have updated your files, reviewed and committed them, you must then **Push** them to the remote repository to allow others to access your changes. This is done in Visual Studio for Mac by selecting **Version Control > Push Changes**. This will display the Push dialog, allowing you to view the committed changes, and select the branch to push to:
 
 ![Dialog showing the branch to commit to](media/version-control-gitPush.png)
 
@@ -52,11 +52,11 @@ These allow the following actions:
 
 * **Merge** – This can be used if you have a merge conflict when committing your work. It shows a visual representation of the changes made by you and the other developer, allowing you to combine both sections of code cleanly. 
 
-## Switching Branches 
+## Switching branches 
 
 By default, the first branch created in a repository is known as the **Master** branch. There isn't technically anything different between the master branch and any other, but the master branch is the one that is most often thought of in development teams as the 'live' or 'production' branch.
 
-An independent line of development can be created by branching off Master (or any other branch, for that matter). This provides a new version of the master branch at a particular point in time, allowing developing independently from that is 'live.' Using branches in this way is often used for features in software development
+An independent line of development can be created by branching off Master (or any other branch, for that matter). This provides a new version of the master branch at a point in time, allowing for development independently of what is 'live.' Using branches in this way is often used for features in software development
 
 Users can create as many branches as they like for each repository, but it is recommended that once they have finished using a branch, it is deleted it to keep the repository organized.
 
@@ -76,9 +76,9 @@ See the current branch in the Solution Pad, next to the project name:
 
  ![Current branch displayed in solution pad](media/version-control-gitBranchName.png)
 
-## Reviewing and Committing 
+## Reviewing and committing 
 
-To review changes in the files, use the Changes, Blame, Log, and Merge tabs on each document, illustrated earlier in this document.
+To review changes in the files, use the Changes, Blame, Log, and Merge tabs on each document, illustrated earlier in this topic.
 
 Review all changes in your project by browsing to the **Version Control > Review Solution and Commit** menu item:
 
diff --git a/mac/working-with-subversion.md b/mac/working-with-subversion.md
@@ -10,31 +10,31 @@ ms.assetid: 2400ED9C-6236-4C0A-A3AB-9D7CBE1F0CF4
 
 # Working with Subversion
 
-As mentioned earlier in this article, Subversion is the centralized version control system that enables you to check out a single master copy of the centralized data. In contrast to Git, checking out a Subversion repository does not clone the entire repository, it only takes a snapshot of that point in time.
+As mentioned earlier in this article, Subversion is the centralized version control system that enables you to check out a single master copy of the centralized data. In contrast to Git, checking out a Subversion repository does not clone the entire repository, it only takes a snapshot at that point in time.
 
 Subversion uses a copy-modify-merge model to allow users to work on the same repository simultaneously. This means that each user creates a local, or working, copy of the centralized data, which they can then work on independently. The changes to users working copies are merged in a chronological fashion.
 
-For example, imagine User A and User B each check out a copy from the remote repository and they each modify files. User A finishes the modifications and commits them remotely. Before User B commits their work, they will have to update their working copy with changes from the remote, thereby merging in User A's changes.
+For example, imagine that User A and User B both check out a copy from the remote repository and they each modify files. User A finishes the modifications and commits them remotely. Before User B commits their work, they will have to update their working copy with changes from the remote, thereby merging in User A's changes.
 
 In the sections below we will explore how Subversion can be used for version control in Visual Studio for Mac.
 
 The image below illustrates the options provided by Visual Studio for Mac by the Version Control menu item:
 
 ![Version Control menu items](media/version-control-svnVersionControlMenu.png)
 
-The sections below will explain each in more detail.
+The sections below will explain each option in more detail.
 
 ## Checkout…
 
 Before starting to use a remote Subversion repository, you will need to check out the repo to create a local, or working, copy of that directory on your local machine.
 
-To check out using the **Checkout** feature in Visual Studio for Mac, follow the steps in the [Setting up a Subversion repository](~/set-up-subversion-repository.md) section.
+To find out about using the **Checkout** feature in Visual Studio for Mac, follow the steps in the [Setting up a Subversion repository](~/set-up-subversion-repository.md) section.
 
-## Update Solution
+## Update solution
 
 When using a remote repository, it is important to remember that other users may be modifying files, making your working copy outdated. In anticipation of this, it is always recommended to pull any changes from the repository into your solution before starting work, and before committing. To do this, select the *Version Control > Update Solution* menu item.
 
-## Review Solution and Commit
+## Review solution and commit
 
 To review changes in files, use the Changes, Blame, Log, and Merge tabs on each document, as illustrated below:
 
