Merge pull request #860 from mikeblome/mb-intell

fixed IntelliSense casing across repo

Author: PRMerger6

docs/cppcx/platform-array-class.md

@@ -51,7 +51,7 @@ private ref class Array<TArg, 1> :
   
  The Windows Runtime type system does not support the concept of jagged arrays and therefore you cannot pass an IVector<Platform::Array\<T>> as a return value or method parameter. To pass a jagged array or a sequence of sequences across the ABI, use `IVector<IVector<T>^>`.  
   
- This class is defined in the vccorlib.h header, which is automatically included by the compiler. It is visible in Intellisense but not in Object Browser because it is not a public type defined in platform.winmd.  
+ This class is defined in the vccorlib.h header, which is automatically included by the compiler. It is visible in IntelliSense but not in Object Browser because it is not a public type defined in platform.winmd.  
   
 ### Requirements  
  Compiler option: **/ZW**  

docs/ide/how-to-enable-intellisense-for-makefile-projects.md

@@ -35,7 +35,7 @@ IntelliSense fails to operate in the IDE for Visual C++ makefile projects when c
 
     -   Set the **Forced Using Assemblies** property to specify which .NET assemblies to process when building your makefile project. See [/FU (Name Forced #using File)](../build/reference/fu-name-forced-hash-using-file.md), for more information.  
 
-    -   Set the **Additional Options** property to specify additional compiler switches to be used by Intellisense when parsing C++ files.  
+    -   Set the **Additional Options** property to specify additional compiler switches to be used by IntelliSense when parsing C++ files.  
 
 4.  Click **OK** to close the property pages.  
 

docs/ide/how-to-organize-project-output-files-for-builds.md

@@ -20,7 +20,7 @@ This topic describes best practices for organizing project output files. Build e
 
 1.  You can reference an assembly directly from your code by using the #using directive, such as `#using <System.Data.dll>`. For more information, see [#using Directive](../preprocessor/hash-using-directive-cpp.md).  
 
-     The file specified can be a .dll, .exe, .netmodule, or .obj, as long as it is in MSIL. The referenced component can be built in any language. Using this option, you will have access to Intellisense since the metadata will be extracted from the MSIL. The file in question must be in the path for the project; otherwise, the project will not compile and Intellisense will not be available. An easy way to determine whether the file is in the path is to right-click on the #using line and choose the **Open document** command. You will be notified if the file cannot be found.  
+     The file specified can be a .dll, .exe, .netmodule, or .obj, as long as it is in MSIL. The referenced component can be built in any language. Using this option, you will have access to IntelliSense since the metadata will be extracted from the MSIL. The file in question must be in the path for the project; otherwise, the project will not compile and IntelliSense will not be available. An easy way to determine whether the file is in the path is to right-click on the #using line and choose the **Open document** command. You will be notified if the file cannot be found.  
 
      If you do not want to put the full path to the file, you can use the **/AI** compiler option to edit the search path for #using references. For more information, see [/AI (Specify Metadata Directories)](../build/reference/ai-specify-metadata-directories.md).  
 

docs/ide/ide-and-tools-for-visual-cpp-development.md

@@ -19,7 +19,7 @@ In addition to shared tools in the Visual Studio IDE, MSVC has several tools spe
 
 ## Creating a solution and project(s)
 
-A *project* is basically a set of source code files and resources such as images or data files that are built into an executable file. Visual Studio 2017 can support any build system or custom build tools that you wish to use, with full support for Intellisense, browsing and debugging:
+A *project* is basically a set of source code files and resources such as images or data files that are built into an executable file. Visual Studio 2017 can support any build system or custom build tools that you wish to use, with full support for IntelliSense, browsing and debugging:
 
 - MSBuild is the native build system for Visual Studio and is often the best choice for Universal Windows Platform (UWP) apps or legacy Windows desktop applications that use MFC or ATL. For more information about MSBuild-based C++ projects, see [Creating and managing MSBuild-based projects](creating-and-managing-visual-cpp-projects.md).
 - CMake is a cross-platform build system that is integrated into the Visual Studio IDE when you install the Desktop development with C++ workload. For more information, see [CMake projects in Visual C++](cmake-tools-for-visual-cpp.md).
@@ -47,13 +47,13 @@ For more information about creating a user interface for an MFC application, see
 
 After you create a project, all the project files are displayed in the **Solution Explorer** window. When you click on a .h or .cpp file in **Solution Explorer**, the file opens up in the code editor. The code editor is a specialized word processor for C++ source code. It color-codes language keywords, method and variable names, and other elements of your code to make the code more readable and easier to understand.
 
-### Intellisense
+### IntelliSense
 
-The code editor also supports several features that together are known as Intellisense. You can hover over a method and see some basic documentation for it. After you type a class variable name and a . or ->, a list of instance members of that class appears. If you type a class name and then a ::, a list of static members appears. When you start typing a class or method name, the code editor will offer suggestions to complete the statement. For more information, see [Using IntelliSense](/visualstudio/ide/using-intellisense).
+The code editor also supports several features that together are known as IntelliSense. You can hover over a method and see some basic documentation for it. After you type a class variable name and a . or ->, a list of instance members of that class appears. If you type a class name and then a ::, a list of static members appears. When you start typing a class or method name, the code editor will offer suggestions to complete the statement. For more information, see [Using IntelliSense](/visualstudio/ide/using-intellisense).
 
 ### Code snippets
 
-You can use Intellisense code snippets to generate commonly-used or complicated code constructs with a shortcut keystroke. For more information, see [Code Snippets](/visualstudio/ide/code-snippets).
+You can use IntelliSense code snippets to generate commonly-used or complicated code constructs with a shortcut keystroke. For more information, see [Code Snippets](/visualstudio/ide/code-snippets).
 
 ## Navigating code
 

docs/ide/writing-and-refactoring-code-cpp.md

@@ -16,7 +16,7 @@ ms.workload: ["cplusplus"]
 
 The Visual C++ code editor and IDE provide many coding aids. Some are unique to C++, and some are essentially the same for all Visual Studio languages. For more information about the shared features, see [Writing Code in the Code and Text Editor](/visualstudio/ide/writing-code-in-the-code-and-text-editor). Options for enabling and configuring C++-specific features are located under **Tools | Options | Text Editor | C/C++**. After choosing which option you want to set, you can get more help by pressing **F1** when the dialog is in focus. For general code formatting options, type `Editor C++` into **QuickLaunch**.
 
-Experimental features, which may or may not be included in a future version of Visual Studio, are found in the [Text Editor C++ Experimental](/visualstudio/ide/reference/options-text-editor-c-cpp-experimental) dialog. In Visual Studio 2017 you can enable **Predictive Intellisense** in this dialog.
+Experimental features, which may or may not be included in a future version of Visual Studio, are found in the [Text Editor C++ Experimental](/visualstudio/ide/reference/options-text-editor-c-cpp-experimental) dialog. In Visual Studio 2017 you can enable **Predictive IntelliSense** in this dialog.
 
 ## Adding new files
 
@@ -34,7 +34,7 @@ IntelliSense is the name for a set of features that provide inline information a
 
 ![C++ member list drop down](../ide/media/vs2015_cpp_statement_completion.png "vs2015_cpp_statement_completion")
 
-For complete information see [Visual C++ Intellisense](/visualstudio/ide/visual-cpp-intellisense).
+For complete information see [Visual C++ IntelliSense](/visualstudio/ide/visual-cpp-intellisense).
 
 ## Insert Snippets
 

docs/ide/xml-documentation-visual-cpp.md

@@ -14,7 +14,7 @@ ms.workload: ["cplusplus"]
 # XML Documentation (Visual C++)
 In Visual C++, you can add comments to your source code that will be processed to an .xml file. This file can then be the input to a process that creates documentation for the classes in your code.  
 
- In a Visual C++ code file, XML documentation comments must be located directly prior to a method or type definition. The comments can be used to populate the Intellisense QuickInfo data tip in the following scenarios:  
+ In a Visual C++ code file, XML documentation comments must be located directly prior to a method or type definition. The comments can be used to populate the IntelliSense QuickInfo data tip in the following scenarios:  
 
 1.  when the code is compiled as a Windows Runtime component with an accompanying .winmd file  
 

docs/linux/prop-pages/directories-linux.md

@@ -16,5 +16,5 @@ Property | Description
 --- | ---
 Include Directories | Path to use when searching for include files while building a VC++ project.  Corresponds to environment variable INCLUDE.
 Library Directories | Path to use when searching for library files while building a VC++ project.  Corresponds to environment variable LIB.
-Source Directories | Path to use when searching for source files to use for Intellisense.
+Source Directories | Path to use when searching for source files to use for IntelliSense.
 Exclude Directories | Path to skip when searching for scan dependencies.

docs/linux/prop-pages/makefile-linux.md

@@ -84,7 +84,7 @@ Include Search Path | Specifies the include search path for resolving included f
 Forced Includes | Specifies the files that are forced included.
 Preprocessor Definitions | Specifies the preprocessor defines used by the source files.
 Undefine Preprocessor Definitions | Specifies one or more preprocessor undefines.     (/U[macro])
-Additional Options | Specifies additional compiler switches to be used by Intellisense when parsing C++ files.
+Additional Options | Specifies additional compiler switches to be used by IntelliSense when parsing C++ files.
 
 ### Build
 

docs/vcpkg.md

@@ -112,7 +112,7 @@ Run **vcpkg integrate install** to configure Visual Studio to locate all vcpkg h
 
 Now you can #include headers simply by typing the folder/header, and auto-complete assists you. No additional steps are required for linking to libs or adding project references. The following illustration shows how Visual Studio finds the azure-storage-cpp headers. vcpkg places its headers in the **/installed** subfolder, partitioned by target platform. The following diagram shows the list of include files in the **/was** subfolder for the library:
 
-![vcpkg Intellisense integration](media/vcpkg-intellisense.png "vcpkg and Intellisense")
+![vcpkg IntelliSense integration](media/vcpkg-intellisense.png "vcpkg and IntelliSense")
 
 ### Per project