Update per Acquent requests.

Author: Greg Van Liew

docs/extensibility/open-folder.md

@@ -1,5 +1,5 @@
 ---
-title: "Visual Studio Open Folder Extensibility Overview | Microsoft Docs"
+title: "Visual Studio Open Folder extensibility overview | Microsoft Docs"
 ms.custom: ""
 ms.date: "02/21/2018"
 ms.reviewer: ""
@@ -15,7 +15,7 @@ manager: "viveis"
 ms.workload:
   - "vssdk"
 ---
-# Open Folder Extensibility
+# Open Folder extensibility
 
 The [Open Folder](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) feature allows users to open any codebase in Visual Studio without the need for project or solution files. Open Folder provides the features users expect from Visual Studio such as:
 
@@ -53,6 +53,6 @@ Features that use the following types will need to adopt new APIs to support Ope
 
 Open Folder and the `Microsoft.VisualStudio.Workspace.*` APIs are under active development. If you see unexpected behavior, then see the known issues for the release of interest. The Developer Community is the recommended place to vote and create any issues. For each feedback, we highly recommend a detailed description of your issue. Include the Visual Studio version you're developing for, the APIs you're using (both what you've implemented and what you're interacting with), the expected outcome, and the actual outcome. If possible, include a dump of the devenv.exe process. Use GitHub's issue tracking for giving feedback on this and related documentation.
 
-## Next Steps
+## Next steps
 
 * [Workspaces](workspaces.md) - Learn about the Open Folder workspace API.

docs/extensibility/workspace-build.md

@@ -1,5 +1,5 @@
 ---
-title: "Workspace Build in Visual Studio | Microsoft Docs"
+title: "Workspace build in Visual Studio | Microsoft Docs"
 ms.custom: ""
 ms.date: "02/21/2018"
 ms.reviewer: ""
@@ -15,11 +15,11 @@ manager: "viveis"
 ms.workload:
   - "vssdk"
 ---
-# Workspace Build
+# Workspace build
 
 Build support in [Open Folder](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) scenarios requires an extender to supply [indexed](workspace-indexing.md) and [file context](workspace-file-contexts.md) data for the [workspace](workspaces.md), as well as the build action to run.
 
-Below is an outline of what your extension will need:
+Below is an outline of what your extension will need.
 
 ## Build file context
 
@@ -103,4 +103,8 @@ Alternatively, extensions can directly interact with the **Error List** or **Bui
 
 ## tasks.vs.json and launch.vs.json
 
-For information on authoring a tasks.vs.json or launch.vs.json file, see [Customize build and debug tasks](../ide/customize-build-and-debug-tasks-in-visual-studio.md).
+For information on authoring a tasks.vs.json or launch.vs.json file, see [Customize build and debug tasks](../ide/customize-build-and-debug-tasks-in-visual-studio.md).
+
+## Next steps
+
+* [Language Server Protocol](language-server-protocol.md) - Learn how to integrate language servers into Visual Studio.

docs/extensibility/workspace-file-contexts.md

@@ -1,5 +1,5 @@
 ---
-title: "Workspace File Contexts in Visual Studio | Microsoft Docs"
+title: "Workspace file contexts in Visual Studio | Microsoft Docs"
 ms.custom: ""
 ms.date: "02/21/2018"
 ms.reviewer: ""
@@ -15,7 +15,7 @@ manager: "viveis"
 ms.workload:
   - "vssdk"
 ---
-# Workspace File Contexts
+# Workspace file contexts
 
 All insights into [Open Folder](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) workspaces are produced by "file context providers" that implement the <xref:Microsoft.VisualStudio.Workspace.IFileContextProvider> interface. These extensions might look for patterns in folders or files, read MSBuild files and makefiles, detect package dependencies, etc. in order to accumulate the insights they need to define a file context. A file context by itself does not perform any action, but rather provides data that another extension can then act on.
 
@@ -72,7 +72,7 @@ A workspace listens to file change notifications and provides the <xref:Microsof
 >[!TIP]
 >A workspace's [indexing service](workspace-indexing.md) subscribes to file events by default. File additions and modifications will cause relevant `IFileScanner`s events to be invoked for new data for that file. File deletions will remove indexed data. You don't need to subscribe your `IFileScanner` to the file watcher service.
 
-## Next Steps
+## Next steps
 
 * [Indexing](workspace-indexing.md) - Workspace indexing collects and persists information about the workspace.
 * [Workspaces](workspaces.md) - Review workspace concepts and settings storage.

docs/extensibility/workspace-indexing.md

@@ -1,5 +1,5 @@
 ---
-title: "Workspace Indexing in Visual Studio | Microsoft Docs"
+title: "Workspace indexing in Visual Studio | Microsoft Docs"
 ms.custom: ""
 ms.date: "02/21/2018"
 ms.reviewer: ""
@@ -15,7 +15,7 @@ manager: "viveis"
 ms.workload:
   - "vssdk"
 ---
-# Workspace Indexing
+# Workspace indexing
 
 In a solution, project systems are responsible for providing functionality for build, debug, **GoTo** symbol searching, and more. Project systems can do this work because they understand the relation and capabilities of files within a project. An [Open Folder](../ide/develop-code-in-visual-studio-without-projects-or-solutions.md) workspace needs the same insight to provide rich IDE features as well. The collection and persistent storage of this data is a process called workspace indexing. This indexed data can be queried through a set of asynchronous APIs. Extenders can participate in the indexing process by providing <xref:Microsoft.VisualStudio.Workspace.Indexing.IFileScanner>s that know how to handle certain types of files.
 
@@ -67,7 +67,7 @@ Extensions can export a scanner by implementing `IWorkspaceProviderFactory<IFile
 
 In advanced situations, an extension might dynamically support an arbitrary set of file types. Rather than MEF exporting `IWorkspaceProviderFactory<IFileScanner>`, an extension can export `IWorkspaceProviderFactory<IFileScannerProvider>`. When indexing begins, this factory type will be imported, instantiated, and have its <xref:Microsoft.VisualStudio.Workspace.Indexing.IFileScannerProvider.GetSymbolScannersAsync%2A> method invoked. `IFileScanner` instances supporting any value from `FileScannerTpeConstants` will be honored, not just symbols.
 
-## Next Steps
+## Next steps
 
 * [Workspaces and language services](workspace-language-services.md) - Learn how to integrate language services into an Open Folder workspace.
 * [Workspace build](workspace-build.md) - Open Folder supports build systems such as MSBuild and makefiles.

docs/extensibility/workspace-language-services.md

@@ -1,5 +1,5 @@
 ---
-title: "Workspaces Language Services in Visual Studio | Microsoft Docs"
+title: "Workspaces and language services in Visual Studio | Microsoft Docs"
 ms.custom: ""
 ms.date: "02/21/2018"
 ms.reviewer: ""
@@ -25,7 +25,7 @@ In a [workspace](workspaces.md), language services are initialized by an <xref:M
 
 When a document is opened in the editor, Visual Studio only considers language service providers that require file context types for which a matching file context provider can be found. It then passes the file context(s) from the matching provider(s) to the selected language service provider via `ILangaugeServiceProvider.InitializeAsync`. What the language service provider does with that file context data is an implementation detail of the language service provider, but the expected user experience is a richer language service for that opened document.
 
-## Using `ILanguageServiceProvider`
+## Using ILanguageServiceProvider
 
 The language service will be notified when a file context is created with a `ContextType` that matches one of the `SupportedContextTypes` values of the language server export attribute.
 
@@ -59,6 +59,6 @@ The `Microsoft.VisualStudio.Workspace.*` APIs aren't the only way to enable your
 
 - <xref:Microsoft.VisualStudio.Workspace.Intellisense.ILanguageServiceProvider> is invoked when a file of matching file types is opened or closed for editing.
 
-## Next Steps
+## Next steps
 
 * [Workspace build](workspace-build.md) - Open Folder supports build systems such as MSBuild and makefiles. 

docs/extensibility/workspaces.md

@@ -174,11 +174,11 @@ A UI context can be used to auto-load your package. The value is `4646B819-1AE0-
 
 ## Troubleshooting
 
-### The 'SourceExplorerPackage' package did not load correctly
+### The SourceExplorerPackage package did not load correctly
 
 Workspace extensibility is heavily MEF-based, and composition errors will cause the package hosting Open Folder to fail to load. For example, if an extension exports a type with `ExportFileContextProviderAttribute`, but the type only implements `IWorkspaceProviderFactory<IFileContextActionProvider>`, an error will occur when trying to open a folder in Visual Studio. Error details can be found in _%LOCALAPPDATA%\Microsoft\VisualStudio\15.0_id\ComponentModelCache\Microsoft.VisualStudio.Default.err_. Resolve any errors for types implemented by your extension.
 
-## Next Steps
+## Next steps
 
 * [File contexts](workspace-file-contexts.md) - File context providers bring code intelligence for Open Folder workspaces. 
 * [Indexing](workspace-indexing.md) - Workspace indexing collects and persists information about the workspace.