Additional changes for TFVC.

Author: jmatthiesen

mac/tf-version-control.md

@@ -33,20 +33,22 @@ The rest of this article walks you through the options listed above.
 
 ## Use Visual Studio Code and the Azure Repos extension
 
-If you like to work with a graphical interface for managing you local version control, then the Azure Repos extension for Visual Studio Code provides a supported solution from Microsoft. To get started, download [Visual Studio Code](https://code.visualstudio.com) and then learn how to [configure the Azure Repos extension](https://marketplace.visualstudio.com/items?itemName=ms-vsts.team).
+If you like to work with a graphical interface to manage you files in version control, then the Azure Repos extension for Visual Studio Code provides a supported solution from Microsoft. To get started, download [Visual Studio Code](https://code.visualstudio.com) and then learn how to [configure the Azure Repos extension](https://marketplace.visualstudio.com/items?itemName=ms-vsts.team).
 
 ## Connecting using the Team Explorer Everywhere Command Line Client
 
 If you're comfortable using the macOS Terminal, then the Team Explorer Everywhere Command Line Client (TEE-CLC) provides a supported way to connect to your source in TFVC.
 
+You can follow the steps below to set up your connection to TFVC and commit changes.
+
 Special thanks to Chris Pilcher, a developer in our community, who's [original instructions for the TEE-CLC](https://gist.github.com/chris-pilcher/a3f14eb081d7ab983e5c) formed the basis of this section.
 
 ### Setting up the TEE-CLC
 
 There are two ways to get setup with the TEE-CLC.
 
-1. Use Homebrew to install the client.
-1. Download and manually install the client.
+* Use Homebrew to install the client, or
+* Download and manually install the client
 
 The easiest solution is **using HomeBrew**, which is a package manager for macOS. To install using this method:
 
@@ -63,13 +65,13 @@ To **setup the TEE-CLC manually**:
 
 Once the TEE-CLC is installed, you can run the command `tf eula` to view and accept the license agreement for the client.
 
-Finally, to authenticate with your TFS/Azure DevOps environment, you'll need to create a personal access token on the server. Learn more about [authenticating with personal access tokens](https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/pats?view=azure-devops). 
+Finally, to authenticate with your TFS/Azure DevOps environment, you'll need to create a personal access token on the server. Learn more about [authenticating with personal access tokens](https://docs.microsoft.com/en-us/azure/devops/integrate/get-started/authentication/pats?view=azure-devops). When creating a personal access token to use with TFVC, be sure to provide Full Access when configuring the token.
 
 ### Using the TEE-CLC to connect to your repo
 
 To connect to your source code, you first need to create a workspace using the `tf workspace` command. For example, the following commands connect to an Organization in Azure DevOps Services called "MyOrganization": 
 
-```
+```bash
 export TF_AUTO_SAVE_CREDENTIALS=1
 tf workspace -new MyWorkspace -collection:https://dev.azure.com/MyOrganization
 ```
@@ -78,21 +80,21 @@ The `TF_AUTO_SAVE_CREDENTIALS` environment setting is used to save your credenti
 
 Now, to create a mapping of your source files to a local folder, you'll use the `tf workfold` command. The following example will map a folder named "WebApp.Services" from the "MyRepository" TFVC project and set it up to be copied into the local ~/Projects/ folder (i.e. a "Projects" folder in the current users's home folder).
 
-```
+```bash
 tf workfold -map $/MyRepository/WebApp.Services -workspace:MyWorkspace ~/Projects/
 ```
 
 Finally, you use the following command to get the source files from the server and copy them locally:
 
-```
+```bash
 tf get
 ```
 
 ### Committing changes using the TEE-CLC
 
 After you've made changes to your files in Visual Studio for Mac, you can switch back to the Terminal to check in your edits. The `tf add` command is used to add files to the list of pending changes to be checked-in and the `tf checkin` command performs the actual check-in to the server. The `checkin` command includes parameters to add a comment or associate a related work item. In the following code snippet, all files in a `WebApp.Services` folder are added, recursively, to the checkin. Then, the code is checked in with a comment and associated with a work item with the ID "42".
 
-```
+```bash
 cd WebApp.Services
 tf add * /recursive
 tf checkin -comment:"Replaced 'Northwand' typos with the correct word Northwind" -associate:42