fixed broken anchors (#1194)

* fixed broken anchors
* fixed more links

* fixed more links

* fixed links

* fixed more links

* fixed casing

* more fixes

* more fixes

Author: mairaw

docs/core/tools/dotnet-install-script.md

@@ -2,7 +2,8 @@
 title: dotnet-install scripts | .NET Core SDK
 description: Learn about the dotnet-install scripts to install the .NET Core CLI tools and the shared runtime. 
 keywords: dotnet-install, dotnet-install scripts, .NET Core
-author: mairaw
+author: blackdwarf
+ms.author: mairaw
 manager: wpickett
 ms.date: 10/12/2016
 ms.topic: article
@@ -42,7 +43,7 @@ By default, the script will add the install location to the $PATH for the curren
 
 Before running the script, please install all the required [dependencies](https://github.com/dotnet/core/blob/master/Documentation/prereqs.md).
 
-You can install a specific version using the `--version` argument. The version needs to be specified as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) file found in the hierarchy above the folder where the script was invoked in that contains the `sdkVersion` property. If that is not present, it will use Latest.
+You can install a specific version using the `--version` argument. The version needs to be specified as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) file found in the hierarchy above the folder where the script was invoked that contains the `version` property. If that is not present, it will use Latest.
 
 You can also use this script to get the SDK or shared runtime debug binaries with debug symbols by using the `--debug` argument. If you do not do this on first install and realize you do need debug symbols later on, you can re-run the script with this argument and the version of the bits you installed. 
 
@@ -56,7 +57,7 @@ Which channel (for example, `future`, `preview`, `production`) to install from.
 
 `-Version [VERSION]`
 
-Which version of CLI to install; you need to specify the version as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) that contains the [sdkVersion](global-json.md#sdkversion) property; if that is not present, it will use Latest. 	
+Which version of CLI to install; you need to specify the version as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) that contains the `version` property; if that is not present, it will use Latest. 	
 
 `-InstallDir [DIR]`
 
@@ -83,7 +84,7 @@ Which channel (for example "future", "preview", "production") to install from. T
 
 `--version [VERSION]`
 
-Which version of CLI to install; you need to specify the version as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) that contains the [sdkVersion](global-json.md#sdkversion) property; if that is not present, it will use Latest. 	
+Which version of CLI to install; you need to specify the version as 3-part version (for example, 1.0.0-13232). If omitted, it will default to the first [global.json](global-json.md) that contains the `version` property; if that is not present, it will use Latest. 	
 
 `--install-dir [DIR]`
 

docs/core/tools/index.md

@@ -2,7 +2,8 @@
 title: .NET Core Command-Line Interface (CLI) Tools
 description: An overview of what the Command-Line Interface (CLI) is and its main features
 keywords: CLI, CLI tools, .NET, .NET Core
-author: mairaw
+author: blackdwarf
+ms.author: mairaw
 manager: wpickett
 ms.date: 10/06/2016
 ms.topic: article
@@ -12,11 +13,9 @@ ms.devlang: dotnet
 ms.assetid: b70e9ac0-c8be-49f7-9332-95ab93e0e7bc
 ---
 
-# .NET Core Command-Line Interface Tools
+# .NET Core command-line interface tools
 
-By [Zlatko Knezevic](https://github.com/blackdwarf) and [Maira Wenzel](https://github.com/mairaw)
-
-The .NET Core Command-Line Interface (CLI) is a new foundational cross-platform toolchain for developing 
+The .NET Core command-line interface (CLI) is a new foundational cross-platform toolchain for developing 
 .NET Core applications. It is "foundational" because it is the primary layer on which other, 
 higher-level tools, such as Integrated Development Environments (IDEs), editors and 
 build orchestrators can build on. 
@@ -90,7 +89,7 @@ specify a portable app DLL that `dotnet` would run similar to this: `dotnet /pat
 
 In the second case, the driver attempts to invoke the specified command. This starts the CLI command execution 
 process. First, the driver determines the version of the tooling that you want. You can specify the version in the 
-[global.json](global-json.md) file using the [sdkVersion](global-json.md#sdkversion) property. If that is not available, the driver finds the latest version
+[global.json](global-json.md) file using the `version` property. If that is not available, the driver finds the latest version
 of the tools that is installed on disk and uses that version. Once the version is determined, it executes the 
 command. 
 
@@ -127,4 +126,4 @@ in the [.NET Core CLI extensibility model](extensibility.md) topic.
 This was a short overview of the most important features of the CLI. You can find out more by using the reference and 
 conceptual topics on this site. There are also other resources you can use:
 * [dotnet/CLI](https://github.com/dotnet/cli/) GitHub repo
-* [Getting Started instructions](https://aka.ms/dotnetcoregs/)
+* [Getting started instructions](https://aka.ms/dotnetcoregs/)

docs/core/tools/project-json.md

@@ -3,6 +3,7 @@ title: project.json reference
 description: project.json reference
 keywords: .NET, .NET Core, project.json
 author: aL3891
+ms.author: mairaw
 manager: wpickett
 ms.date: 09/30/2016
 ms.topic: article
@@ -363,10 +364,10 @@ Type: String
 Specifies the type of the dependency. It can be one of the following values: `default`, `build` or `platform`. The default value is `default`.
 
 `build` is known as a development dependency and is only used for build-time. It means that the package should not be published or added as a dependency to the output `.nupkg` file. 
-It has the same effect of setting [supressParent](#supressParent) to `all`.
+It has the same effect of setting [supressParent](#supressparent) to `all`.
 
 `platform` references the shared SDK. For more information, see the section on "Deploying a framework-dependent deployment with third-party dependencies" on the 
-[.NET Core Application Deployment](../deploying/index.md) topic.
+[.NET Core application deployment](../deploying/index.md) topic.
 
 For example:
 

docs/csharp/csharp-7.md

@@ -3,6 +3,7 @@ title: What's New in C# 7 | C# Guide
 description: Get an overview of the new features coming in the upcoming version 7 of the C# language.    
 keywords: C#, .NET, .NET Core, Latest Features, What's New
 author:  BillWagner
+ms.author: wiwagn
 manager: wpickett
 ms.date: 10/03/2016
 ms.topic: article
@@ -20,15 +21,15 @@ C# 7 adds a number of new features to the C# language:
 * [Tuples](#tuples)
 * [Pattern Matching](#pattern-matching)
 * [`ref` locals and returns](#ref-locals-and-returns)
-* [Local Functions](#local-expressions)
-* [Expression Bodied Everything](#expression-bodied-everything)
-* [`throw` Expressions](#throw-expressions)
+* [Local Functions](#local-functions)
+* [Expression Bodied Everything](#expression-bodied-everything-preview-5)
+* [`throw` Expressions](#throw-expressions-preview-5)
 * [Generalized async return types](#generalized-async-return-types)
 * [Numeric literal syntax improvements](#numeric-literal-syntax-improvements)
 
 Two of the most interesting features don't make that list. The first
 is the shortened release cycle. C# 7 is following C# 6 much more quickly.
-The second is that C# 7 has [features contributed by the community](#expression-bodied-everything), not
+The second is that C# 7 has [features contributed by the community](#expression-bodied-everything-preview-5), not
 the C# compiler team. The language is truly open.
 
 The remainder of this topic provides an overview 

docs/fsharp/tutorials/getting-started/getting-started-visual-studio.md

@@ -3,45 +3,46 @@ title: Getting Started with F# in Visual Studio
 description: Learn how to use F# with Visual Studio.
 keywords: visual f#, f#, functional programming
 author: cartermp
-manager: danielfe
+ms.author: phcart
+manager: wpickett
 ms.date: 09/08/2016
 ms.topic: article
 ms.prod: visual-studio-dev14
 ms.technology: devlang-fsharp
 ms.assetid: 8db75596-19a9-4eda-b20d-a12d517c8cc1 
 ---
 
-# Getting Started with F# in Visual Studio
+# Getting started with F# in Visual Studio
 
 F# and the Visual F# tooling are supported in the Visual Studio IDE.  To begin, you should [download Visual Studio](https://www.visualstudio.com/downloads/download-visual-studio-vs), if you haven't already.  This article uses the Visual Studio 2015 Community Edition, but you can use F# with the version of your choice.
 
-## Installing the Visual F# Tools
+## Installing the Visual F# tools
 
 Visual Studio will first initialize the installer.  After it is intilized, select **Custom** as shown here:
 
-![](media/getting-started-vs/vs2015-install-1.png)
+![Select Custom install](./media/getting-started-vs/vs2015-install-1.png)
 
 Select the Visual F# Tools under Programming Languages here:
 
-![](media/getting-started-vs/vs2015-install-2.png)
+![Visual F#](./media/getting-started-vs/vs2015-install-2.png)
 
 Feel free to customize your installation further, and then continue with the installation.  After a while, Visual Studio will complete installation and you can create an F# project!
 
-## Creating a Console Application
+## Creating a console application
 
 One of the most basic projects in Visual Studio is the Console Application.  Here's how to do it.  Once Visual Studio is open:
 
 1. On the **File** menu, point to **New**, and then choose **Project**.
 
-![](media/getting-started-vs/vs2015-install-3.png)
+![File New Project](./media/getting-started-vs/vs2015-install-3.png)
 
 2.  In the New Project dialog, under **Templates**, you should see **Visual F#**.  Choose this to show the F# templates.
 
-![](media/getting-started-vs/vs2015-install-4.png)
+![Visual F# templates](./media/getting-started-vs/vs2015-install-4.png)
 
 3. Choose the **Okay** button to create the F# project!  You should see something like this under **Solution Explorer**:
 
-![](media/getting-started-vs/vs2015-install-5.png)
+![F# Project in Solution Explorer](./media/getting-started-vs/vs2015-install-5.png)
 
 ## Writing your code
 
@@ -61,7 +62,7 @@ Another function, `main`, is defined, which is decorated with the `EntryPoint` a
 
 It is in this function that we call the `square` function with an argument of `12`.  The F# compiler then assigns the type of `square` to be `int -> int` (that is, a function which takes an `int` and produces an `int`).  The call to `printfn` is a formatted printing function which uses a format string, similar to C-style programming languages, parameters which correspond to those specified in the format string, and then prints the result and a new line.
 
-## Running Your Code
+## Running your code
 
 You can run the code and see results by pressing **ctrl-f5**.  This will run the program without debugging and allows you to see the results.  Alternatively, you can choose the **Debug** top-level menu item in Visual Studio and choose **Start Without Debugging**.
 
@@ -125,18 +126,18 @@ The pipe-forward operator, and more, are covered in later tutorials.
 
 This is only a glimpse into what you can do with F# Interactive.  To learn more, check out [Interactive Programming with F#](../fsharp-interactive/index.md).
 
-## Next Steps
+## Next steps
 
 If you haven't already, check out the [Tour of F#](../../tour.md), which covers some of the core features of the F# language.  It will give you an overview of some of the capabilities of F#, and provide ample code samples that you can copy into Visual Studio and run.  There are also some great external resources you can use, showcased in the [F# Guide](../../index.md).
 
-## See Also
+## See also
 
 [Visual F#](../../index.md)
 
 [Tour of F#](../../tour.md)
 
-[F# Language Reference](../../language-reference/index.md)
+[F# language reference](../../language-reference/index.md)
 
-[Type Inference](../../language-reference/type-inference.md)
+[Type inference](../../language-reference/type-inference.md)
 
-[Symbol and Operator Reference](../../language-reference/symbol-and-operator-reference/index.md)
+[Symbol and operator reference](../../language-reference/symbol-and-operator-reference/index.md)

docs/fsharp/tutorials/getting-started/getting-started-vscode.md

@@ -3,6 +3,7 @@ title: Getting Started with F# in Visual Studio Code with Ionide
 description: Learn how to use F# with Visual Studio Code and the Ionide plugin suite.
 keywords: visual f#, f#, functional programming, .NET, Visual Studio Code, vscode, Ionide
 author: cartermp
+ms.author: phcart
 manager: wpickett
 ms.date: 09/28/2016
 ms.topic: article
@@ -24,7 +25,7 @@ F# 4.0 or higher must be installed on your machine to use Ionide.
 
 If you're on Windows, you have two options for installing F#.
 
-If you've already installed Visual Studio and don't have F#, you can [Install the Visual F# Tools](getting-started-visual-studio.md#installing-the-visual-f#-tools).  This will install all the necessary components to write, compile, and execute F# code.
+If you've already installed Visual Studio and don't have F#, you can [Install the Visual F# Tools](getting-started-visual-studio.md#installing-the-visual-f-tools).  This will install all the necessary components to write, compile, and execute F# code.
 
 If you prefer not to install Visual Studio, use the following instructions: