Fix broken connect links (#1250)

* fix a bad link

* fix broken links

these came in 3 cases.
1. Some links used ... instead of .. to navigate up a folder.
2. Some links were off by one directory up in navigation.
3. Some links used back-slash instead of slash.
4. Typos.

1 and 2 might be significant if we run the migration script again.

* rename getting started with libraries and fix links

The name had an '_ ' and should have '-' instead

* fix build warnings

* wrong API name:  IsUpperCase -> IsUpper

Author: BillWagner

docs/csharp/getting-started/consuming-library-with-visual-studio-2017.md

@@ -15,7 +15,7 @@ ms.assetid: d7b94076-1108-4174-94e7-a18f00072bb7
 
 # Consuming a class library with .NET Core in Visual Studio 2017 #
 
-Once you've followed the steps in [Building a C# class library with .NET Core in Visual Studio 2017 RC](./library-with-visual-studio_2017.md) and [Testing a class library with .NET Core in Visual Studio 2017 RC](testing-library-with-visual-studio.md) to build and test your class library, and you've built a Release version of the library, the next step is to make it available to callers. You can do this in two ways:
+Once you've followed the steps in [Building a C# class library with .NET Core in Visual Studio 2017 RC](./library-with-visual-studio-2017.md) and [Testing a class library with .NET Core in Visual Studio 2017 RC](testing-library-with-visual-studio.md) to build and test your class library, and you've built a Release version of the library, the next step is to make it available to callers. You can do this in two ways:
 
 - If the library will be used by a single solution (for example, if it is a component in a single large application), you can simply include it as a project in your solution.
 
@@ -25,7 +25,7 @@ Once you've followed the steps in [Building a C# class library with .NET Core in
 
 Just as we included unit tests in the same solution as our class library, we can include our application as part of that solution. For example, let's use our class library in a console application that prompts the user to enter a string and reports whether its first charater is uppercase:
 
-1. Open the `ClassLibraryProjects` solution created in the [Building a C# Class Library with .NET Core in Visual Studio 2017 RC](./library-with-visual-studio_2017.md) topic, and in Solution Explorer, open the context menu for the **ClassLibraryProjects** node and choose **Add**, **New Project**.
+1. Open the `ClassLibraryProjects` solution created in the [Building a C# Class Library with .NET Core in Visual Studio 2017 RC](./library-with-visual-studio-2017.md) topic, and in Solution Explorer, open the context menu for the **ClassLibraryProjects** node and choose **Add**, **New Project**.
 
 1. In the **Add New Project** dialog, expand the **Visual C#** and **.NET Core** nodes, and choose the **Console App (.NET Core)** project template, as the following figure shows.
 

docs/csharp/getting-started/library-with-visual-studio_2017.md renamed to docs/csharp/getting-started/library-with-visual-studio-2017.md

@@ -17,7 +17,8 @@ ms.assetid: c849ca26-6a25-4d35-9544-f343af88e0e7
 
 A class library defines types and methods that can be called from any application. A class library developed using .NET Core supports the .NET Standard Library, which allows your library to be called by any .NET platform that supports that version of the .NET Standard Library. When you finish your class library, you can decide whether you want to distribute it as a third-party component, or whether you want to include it as a component that is bundled with one or more applications.
 
-   [!NOTE] For a list of the .NET Standard versions and the platforms they support, see [.NET Standard Library](..\..\standard\library.md).
+> [!NOTE]
+> For a list of the .NET Standard versions and the platforms they support, see [.NET Standard Library](../../standard/library.md).
 
 In this topic, we'll create a simple utility library that contains a single string-handling method. We'll implement it as an [extension method](https://msdn.microsoft.com/en-us/library/bb383977.aspx) so that it can be called as if it were a member of the @System.String class.
 
@@ -55,7 +56,7 @@ Now we can create our class library project:
 
    [!CODE-csharp[ClassLib#1](../../../samples/snippets/csharp/getting_started/with_visual_studio_2017/classlib.cs#1)]
 
-   The class library, `UtilityLibraries.StringLibrary`, contains a method named `StartsWithUpper`, which returns a @System.Boolean value that indicates whether the current string instance begins with an uppercase character. Which characters are uppercase is defined by the Unicode standard. In .NET Core, the [Char.IsUpperCase](xref:System.Char.IsUpperCase(System.Char)) method returns `true` if a character is uppercase.
+   The class library, `UtilityLibraries.StringLibrary`, contains a method named `StartsWithUpper`, which returns a @System.Boolean value that indicates whether the current string instance begins with an uppercase character. Which characters are uppercase is defined by the Unicode standard. In .NET Core, the [Char.IsUpper](xref:System.Char.IsUpper(System.Char)) method returns `true` if a character is uppercase.
 
 1. On the menu bar, choose **Build**, **Build Solution**. The project should compile without error.
 

docs/csharp/getting-started/testing-library-with-visual-studio.md

@@ -15,7 +15,7 @@ ms.assetid: 069ad711-3eaa-45c6-94d7-b40249cc8b99
 
 # Testing a class library with .NET Core in Visual Studio 2017 RC #
 
-In [Building a class library with C# and .NET Core in Visual Studio 2017 RC](library-with-visual-studio.md), we created a simple class library that adds an extension method to the @System.String class. Now, we'll create a unit test to make sure that it works as expected. We'll add our unit test project to the solution we created in the previous topic.
+In [Building a class library with C# and .NET Core in Visual Studio 2017 RC](library-with-visual-studio-2017.md), we created a simple class library that adds an extension method to the @System.String class. Now, we'll create a unit test to make sure that it works as expected. We'll add our unit test project to the solution we created in the previous topic.
 
 ## Creating a unit test project ##
 

docs/csharp/programming-guide/linq-query-expressions/index.md

@@ -91,7 +91,7 @@ translation.priority.ht:
 
 ## See Also  
  [C# Programming Guide](../../../csharp/programming-guide/index.md)   
- [LINQ (Language-Integrated Query)](.../../../csharp/programming-guide/concepts/linq/index.md)   
+ [LINQ (Language-Integrated Query)](../../../csharp/programming-guide/concepts/linq/index.md)   
  [Walkthrough: Writing Queries in C#](../../../csharp/programming-guide/concepts/linq/walkthrough-writing-queries-linq.md)   
  [Basic LINQ Query Operations](../../../csharp/programming-guide/concepts/linq/basic-linq-query-operations.md)   
  [Query Syntax and Method Syntax in LINQ](../../../csharp/programming-guide/concepts/linq/query-syntax-and-method-syntax-in-linq.md)   

docs/standard/choosing-core-framework-server.md

@@ -103,4 +103,4 @@ Some Microsoft or third-party platforms don’t support .NET Core. For example,
 * [.NET Core Guide](../core/index.md)
 * [Porting from .NET Framework to .NET Core](../core/porting/index.md)
 * [.NET Framework on Docker Guide](../framework/index.md)
-* [.NET Components Overview](concepts.md)
+* [.NET Components Overview](components.md)

docs/visual-basic/programming-guide/language-features/linq/index.md

@@ -69,7 +69,7 @@ This section contains overviews, examples, and background information that will
  Provides an example of how to return the results of a LINQ query as a specific type instead of as an anonymous type.  
 
 ## See Also  
- [LINQ (Language-Integrated Query)](../../../visual-basic/programming-guide/concepts/linq/index.md)   
+ [LINQ (Language-Integrated Query)](../../../../visual-basic/programming-guide/concepts/linq/index.md)   
  [Overview of LINQ to XML in Visual Basic](../../../../visual-basic/programming-guide/language-features/xml/overview-of-linq-to-xml.md)   
  [LINQ to DataSet Overview](https://msdn.microsoft.com/library/bb399399)   
  [LINQ to SQL](https://msdn.microsoft.com/library/bb386976)

docs/visual-basic/programming-guide/language-features/procedures/extension-methods.md

@@ -200,7 +200,7 @@ End Module
 ## See Also  
  <xref:System.Runtime.CompilerServices>   
  <xref:System.Runtime.CompilerServices.ExtensionAttribute>   
- [Extension Methods](../../../csharp/programming-guide/classes-and-structs/extension-methods.md)   
+ [Extension Methods](../../../../csharp/programming-guide/classes-and-structs/extension-methods.md)   
  [Module Statement](../../../../visual-basic/language-reference/statements/module-statement.md)   
  [Procedure Parameters and Arguments](./procedure-parameters-and-arguments.md)   
  [Optional Parameters](./optional-parameters.md)