Eliminate elipsis character

Author: Colin Robertson

docs/code-quality/annotating-structs-and-classes.md

@@ -76,7 +76,7 @@ You can annotate struct and class members by using annotations that act like inv
     typedef _Struct_size_bytes_(nSize)  
     struct MyStruct {  
         size_t nSize;  
-        …  
+        ...  
     };  
 
     ```  

docs/code-quality/c6031.md

@@ -104,7 +104,7 @@ _Check_return_ bool func();
 void test_f()  
 {  
     if( func() ) {  
-        // code …  
+        // code ...  
     }  
 }  
 ```  

docs/code-quality/walkthrough-analyzing-managed-code-for-code-defects.md

@@ -160,7 +160,7 @@ In this walkthrough, you analyze a managed project for code defects by using the
 
          Select the **Sign the assembly** check box.  
 
-         In the **Choose a string name key file** list, select **\<New…>**.  
+         In the **Choose a string name key file** list, select **\<New...>**.  
 
          The **Create Strong Name Key** dialog box appears.  
 

docs/cross-platform/build-apps-with-native-ui-using-xamarin-in-visual-studio.md

@@ -112,7 +112,7 @@ Once you've done the steps in [Setup and install](../cross-platform/setup-and-in
 
 1.  To run this sample you must first sign up for a free API key at [http://openweathermap.org/appid](http://openweathermap.org/appid).  
 
-2.  Right-click the **WeatherApp** project and select **Add > Class…**. In the **Add New Item** dialog, name the file **Weather.cs**. You’ll use this class to store data from the weather data service.  
+2.  Right-click the **WeatherApp** project and select **Add > Class...**. In the **Add New Item** dialog, name the file **Weather.cs**. You’ll use this class to store data from the weather data service.  
 
 3.  Replace the entire contents of **Weather.cs** with the following:  
 

docs/cross-platform/learn-app-building-basics-with-xamarin-forms-in-visual-studio.md

@@ -112,7 +112,7 @@ Once you've done the steps in [Setup and install](../cross-platform/setup-and-in
 
  The following steps add then code to the PCL to access and store data from that weather service:  
 
-1.  Right-click the **WeatherApp** project and select **Add > Class…**. In the **Add New Item** dialog, name the file **Weather.cs**. You’ll use this class to store data from the weather data service.  
+1.  Right-click the **WeatherApp** project and select **Add > Class...**. In the **Add New Item** dialog, name the file **Weather.cs**. You’ll use this class to store data from the weather data service.  
 
 2.  Replace the entire contents of **Weather.cs** with the following:  
 

docs/data-tools/add-validation-to-an-n-tier-dataset.md

@@ -50,7 +50,7 @@ Adding validation to a dataset that is separated into an n-tier solution is basi
 ## Validatechanges to individual columns  
  Validate values in individual columns by handling the <xref:System.Data.DataTable.ColumnChanging> event. The <xref:System.Data.DataTable.ColumnChanging> event is raised when a value in a column is modified. Create an event handler for the <xref:System.Data.DataTable.ColumnChanging> event by double-clicking the desired column on the **Dataset Designer**.  
 
- The first time that you double-click a column, the designer generates an event handler for the <xref:System.Data.DataTable.ColumnChanging> event. An `If…Then` statement is also created that tests for the specific column. For example, the following code is generated when you double-click the RequiredDate column on the Northwind Orders table:  
+ The first time that you double-click a column, the designer generates an event handler for the <xref:System.Data.DataTable.ColumnChanging> event. An `If...Then` statement is also created that tests for the specific column. For example, the following code is generated when you double-click the RequiredDate column on the Northwind Orders table:  
 
 ```vb#  
 Private Sub OrdersDataTable_ColumnChanging(ByVal sender As System.Object, ByVal e As System.Data.DataColumnChangeEventArgs) Handles Me.ColumnChanging  

docs/data-tools/create-parameterized-tableadapter-queries.md

@@ -110,7 +110,7 @@ A parameterized query returns data that meets the conditions of a WHERE clause w
 
 1.  In the **Dataset Designer**, select the TableAdapter query that needs to accept null parameter values.  
 
-2.  In the **Properties** window, select**Parameters**.Then press the ellipsis (**…**) button to open the **Parameters Collection Editor**.  
+2.  In the **Properties** window, select**Parameters**.Then press the ellipsis (**...**) button to open the **Parameters Collection Editor**.  
 
 3.  Select the parameter that allows null values and set the **AllowDbNull** property to `true`.  
 

docs/debugger/format-specifiers-in-cpp.md

@@ -95,8 +95,8 @@ int main() {
 |**s32**|UTF-32 string|\<location> U”hello world”|U”hello world”|  
 |**s32b**|UTF-32 string (no quotation marks)|\<location> U”hello world”|hello world|  
 |**en**|enum|Saturday(6)|Saturday|  
-|**hv**|Pointer type - indicates that the pointer value being inspected is the result of the heap allocation of an array, for example, `new int[3]`.|\<location>{\<first member>}|\<location>{\<first member>, \<second member>, …}|  
-|**na**|Suppresses the memory address of a pointer to an object.|\<location>, {member=value…}|{member=value…}|  
+|**hv**|Pointer type - indicates that the pointer value being inspected is the result of the heap allocation of an array, for example, `new int[3]`.|\<location>{\<first member>}|\<location>{\<first member>, \<second member>, ...}|  
+|**na**|Suppresses the memory address of a pointer to an object.|\<location>, {member=value...}|{member=value...}|  
 |**nd**|Displays only the base class information, ignoring derived classes|`(Shape*) square` includes base class and derived class information|Displays only base class information|  
 |hr|HRESULT or Win32 error code. (The debugger now decodes HRESULTs automatically, so this specifier is not required in those cases.|S_OK|S_OK|  
 |wc|Window class flag|0x0010|WC_DEFAULTCHAR|  

docs/debugger/graphics/capturing-graphics-information.md

@@ -59,7 +59,7 @@ Capture graphics information from your Direct3D app so that you can use Visual S
 
      ![Capture frames using the GPU Usage tool.](media/pix_gpu_usage_tool_capture_frame.png)  
 
-     When you're ready to examine the frames you've captured, start the **Visual Studio Graphics Analyzer** by following the **Frame …** link above the image thumbnails, or by double-clicking the thumbnail.  
+     When you're ready to examine the frames you've captured, start the **Visual Studio Graphics Analyzer** by following the **Frame ...** link above the image thumbnails, or by double-clicking the thumbnail.  
 
  Only whole frames can be captured, so when you initiate a capture, it’s really the graphics information from the next frame that's recorded. Recording begins immediately after the frame in which you initiated capture is presented and ends when the captured frame is presented. You can capture as many frames as you want while the app is running under Graphics Diagnostics. If you don't capture any frames, the graphics log is discarded.  
 

docs/debugger/graphics/hlsl-shader-debugger.md

@@ -53,7 +53,7 @@ The HLSL debugger in Visual Studio Graphics Analyzer helps you understand how yo
  Nevertheless, the HLSL debugger provides a better, more CPU-like debugging experience than would be possible otherwise.  
 
 ## HLSL Shader Edit & Apply  
- The HLSL shader debugger doesn't support Edit & Continue in the same way that the CPU debugger does because the GPU execution model doesn't allow shader state to be undone. Instead, the HLSL debugger supports Edit & Apply, which allows you to edit HLSL source files and then choose **Apply** to regenerate the frame to see the effect of your changes. Your modified shader code is stored in a separate file to preserve the integrity of your project's original HLSL source file, but when you're satisfied with your changes you can choose **Copy to…** to copy the changes into your project. Using this feature, you can quickly iterate on shader code that contains errors and eliminate costly rebuild and capture steps from your HLSL debugging workflow.  
+ The HLSL shader debugger doesn't support Edit & Continue in the same way that the CPU debugger does because the GPU execution model doesn't allow shader state to be undone. Instead, the HLSL debugger supports Edit & Apply, which allows you to edit HLSL source files and then choose **Apply** to regenerate the frame to see the effect of your changes. Your modified shader code is stored in a separate file to preserve the integrity of your project's original HLSL source file, but when you're satisfied with your changes you can choose **Copy to...** to copy the changes into your project. Using this feature, you can quickly iterate on shader code that contains errors and eliminate costly rebuild and capture steps from your HLSL debugging workflow.  
 
 ## HLSL Disassembly  
  The HLSL shader debugger provides a listing of HLSL shader assembly to the right of the HLSL source code listing.  

docs/debugger/how-to-debug-aspnet-exceptions.md

@@ -58,4 +58,4 @@ Debugging exceptions is an important part of developing a robust [!INCLUDE[vstec
 
 ### To use best practices for ASP.NET exception handling  
 
--   Place `try … catch` blocks around code that can throw exceptions that you can anticipate and know how to handle. For example, if the application is making calls to an XML Web Service or directly to a SQL Server, that code should be in **try … catch** blocks because there are numerous exceptions that can occur.
+-   Place `try ... catch` blocks around code that can throw exceptions that you can anticipate and know how to handle. For example, if the application is making calls to an XML Web Service or directly to a SQL Server, that code should be in **try ... catch** blocks because there are numerous exceptions that can occur.

docs/debugger/how-to-restore-hidden-debugger-commands.md

@@ -51,7 +51,7 @@ When you set up Visual Studio, you are asked to choose a set of default IDE sett
 
 3.  In the **Menu bar:** drop-down, select the **Debug** menu that you want to contain the restored command.  
 
-4.  Click the **Add Command…** button.  
+4.  Click the **Add Command...** button.  
 
 5.  In the **Add Command** box, select the command you want to add, and click **OK**.  
 

docs/debugger/project-settings-for-a-cpp-debug-configuration.md

@@ -155,7 +155,7 @@ You can change the project settings for a C or Visual C++ debug configuration in
 |**Connection** (Remote Windows Debugger)|Allows you to switch between standard and no-authentication connection types for remote debugging. Specify a remote computer name in the **Remote Server Name** box. Connection types include the following:<br /><br /> -   **Remote with Windows Authentication**<br />-   **Remote with No Authentication**<br /><br /> **Note** Remote debugging with No Authentication may leave the remote computer vulnerable to security violations. Windows Authentication mode is more secure.<br /><br /> For more information, see [Remote Debugging Setup](../debugger/remote-debugging.md).|  
 |**HTTP URL** (Web Service Debugger and Web Browser Debugger)|Specifies the URL where the project you are debugging is located.|  
 |**Debugger Type**|Specifies the type of debugger to be used: **Native Only**, **Managed Only**, **GPU Only**, **Mixed**, **Auto** (default), or **Script**.<br /><br /> -   **Native Only** is for unmanaged C++ code.<br />-   **Managed Only** is for code that runs under the common language runtime (managed code).<br />-   **Mixed** invokes debuggers for both managed and unmanaged code.<br />-   **Auto** determines the debugger type based on compiler and EXE information.<br />-   **Script** invokes a debugger for scripts.<br />-   **GPU Only** is for C++ AMP code that runs on a GPU device or on the DirectX reference rasterizer. See [Debugging GPU Code](../debugger/debugging-gpu-code.md).|  
-|**Environment** (Local Windows Debugger and Remote Windows Debugger)|Specifies environment variables for the program that you are debugging. Use standard environment variable syntax (for example, `PATH="%SystemRoot%\..."`). These variables override the system environment or are merged with the system environment, depending on the **Merge Environment** setting. When you click in the settings column, an "Edit…" appears. Click that link to edit environment variables.|  
+|**Environment** (Local Windows Debugger and Remote Windows Debugger)|Specifies environment variables for the program that you are debugging. Use standard environment variable syntax (for example, `PATH="%SystemRoot%\..."`). These variables override the system environment or are merged with the system environment, depending on the **Merge Environment** setting. When you click in the settings column, an "Edit..." appears. Click that link to edit environment variables.|  
 |**Merge Environment** (Local Windows Debugger)|Determines whether the variables that are specified in the **Environment** box will be merged with the environment that is defined by the operating system. Default setting is Yes.|  
 |**SQL Debugging** (all but MPI Cluster Debugger)|Enables debugging of SQL procedures from your [!INCLUDE[vcprvc](../code-quality/includes/vcprvc_md.md)] application. Default setting is No.|  
 |**Debugging Accelerator Type** (GPU debugging only)|Specifies the GPU device to use for debugging. Installing device drivers for compatible GPU devices will add additional options. The default setting is "GPU - Software Emulator."|  

docs/deployment/clickonce-application-manifest.md

@@ -123,7 +123,7 @@ A [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] application
     </dependentAssembly>  
   </dependency>  
 <publisherIdentity name="CN=DOMAINCONTROLLER\UserMe" issuerKeyHash="18312a18a21b215ecf4cdb20f5a0e0b0dd263c08" /><Signature Id="StrongNameSignature" xmlns="http://www.w3.org/2000/09/xmldsig#">  
-…  
+...  
 </Signature></r:issuer></r:license></msrel:RelData></KeyInfo></Signature></asmv1:assembly>  
 ```  
 

docs/deployment/clickonce-deployment-manifest.md

@@ -126,7 +126,7 @@ A deployment manifest is an XML file that describes a [!INCLUDE[ndptecclick](../
     </dependentAssembly>  
   </dependency>  
 <publisherIdentity name="CN=DOMAIN\MyUsername" issuerKeyHash="18312a18a21b215ecf4cdb20f5a0e0b0dd263c08" /><Signature Id="StrongNameSignature" xmlns="http://www.w3.org/2000/09/xmldsig#">  
-…  
+...  
 </Signature></asmv1:assembly>  
 ```  
 

docs/designers/getting-started-with-wpf.md

@@ -36,10 +36,10 @@ Windows Presentation Foundation (WPF) is a UI framework that creates desktop cli
 
 |||  
 |-|-|  
-|I want to jump right in…|[Walkthrough: My First WPF Desktop Application](../designers/walkthrough-my-first-wpf-desktop-application2.md)<br /><br /> [Walkthrough: Create a WPF Desktop Application connected to an Azure Mobile Service](../designers/walkthrough-create-a-wpf-desktop-application-connected-to-an-azure-mobile-service.md)|  
+|I want to jump right in...|[Walkthrough: My First WPF Desktop Application](../designers/walkthrough-my-first-wpf-desktop-application2.md)<br /><br /> [Walkthrough: Create a WPF Desktop Application connected to an Azure Mobile Service](../designers/walkthrough-create-a-wpf-desktop-application-connected-to-an-azure-mobile-service.md)|  
 |How do I design the application UI?|[Designing XAML in Visual Studio and Blend for Visual Studio](../designers/designing-xaml-in-visual-studio.md)|  
 |New to .NET?|[Overview of the .NET Framework](https://msdn.microsoft.com/en-us/library/zw4w595w\(v=vs.140\).aspx)<br /><br /> [Application Essentials](http://msdn.microsoft.com/Library/653da4ba-3752-4d1f-a08a-de017dc86ecc)<br /><br /> [Getting Started with Visual C# and Visual Basic](https://msdn.microsoft.com/en-us/library/dd492171\(v=vs.140\).aspx)|  
-|Tell me more about WPF…|[Introduction to WPF](../designers/introduction-to-wpf.md)<br /><br /> [XAML Overview (WPF)](https://msdn.microsoft.com/en-us/library/ms752059\(v=vs.100\).aspx)<br /><br /> [Controls](https://msdn.microsoft.com/en-us/library/bb613551\(v=vs.100\).aspx)<br /><br /> [Data Binding Overview](https://msdn.microsoft.com/en-us/library/ms752347\(v=vs.100\).aspx)<br /><br /> [WPF Data Binding with LINQ to XML](../designers/wpf-data-binding-with-linq-to-xml.md)|  
+|Tell me more about WPF...|[Introduction to WPF](../designers/introduction-to-wpf.md)<br /><br /> [XAML Overview (WPF)](https://msdn.microsoft.com/en-us/library/ms752059\(v=vs.100\).aspx)<br /><br /> [Controls](https://msdn.microsoft.com/en-us/library/bb613551\(v=vs.100\).aspx)<br /><br /> [Data Binding Overview](https://msdn.microsoft.com/en-us/library/ms752347\(v=vs.100\).aspx)<br /><br /> [WPF Data Binding with LINQ to XML](../designers/wpf-data-binding-with-linq-to-xml.md)|  
 |Are you a Windows Forms developer?|[Windows Forms Controls and Equivalent WPF Controls](https://msdn.microsoft.com/en-us/library/ms750559\(v=vs.100\).aspx)<br /><br /> [Supported Scenarios in WPF and Windows Forms Interoperation](https://msdn.microsoft.com/en-us/library/ms751797\(v=vs.100\).aspx)|  
 
 ## See Also  

docs/extensibility/creating-a-basic-project-system-part-2.md

@@ -189,7 +189,7 @@ ZipProjects:
 ## Deploying a Visual Studio Template  
  Visual Studio templates do not contain path information. Therefore, the template .zip file must be deployed to a location that is known to Visual Studio. The location of the ProjectTemplates folder is typically **\<%LOCALAPPDATA%>\Microsoft\VisualStudio\14.0Exp\ProjectTemplates**.  
   
- To deploy your project factory, the installation program must have administrator privileges. It deploys templates under the Visual Studio installation node: **…\Microsoft Visual Studio 14.0\Common7\IDE\ProjectTemplates**.  
+ To deploy your project factory, the installation program must have administrator privileges. It deploys templates under the Visual Studio installation node: **...\Microsoft Visual Studio 14.0\Common7\IDE\ProjectTemplates**.  
   
 ## Testing a Visual Studio Template  
  Test your project factory to see whether it creates a project hierarchy by using the Visual Studio template.  

docs/extensibility/extern-element.md

@@ -76,7 +76,7 @@ Extern Element
 <CommandTable xmlns="http://schemas.microsoft.com/VisualStudio/2005-10-  
   18/CommandTable" xmlns:xs="http://www.w3.org/2001/XMLSchema">  
     <Extern href="C:\VSCore\vscommon\inc\vsshlids.h"/>  
-    …  
+    ...  
   <Commands package="guidMyPackage">  
 </CommandTable>  
 ```  

docs/extensibility/how-to-create-an-atom-feed-for-a-private-gallery.md

@@ -57,7 +57,7 @@ You can create an Atom (RSS) feed to an intranet location that contains extensio
 - <entry>  
   <id>SelectionHighlight..a14874d2-8199-4a60-af8a-11d6447813aa</id>   
   <title type="text">Highlight all occurrences of selected word</title>   
-  <summary type="text">This extends the editor to highlight ….</summary>   
+  <summary type="text">This extends the editor to highlight ....</summary>   
   <published>2011-04-14T14:24:51-07:00</published>   
   <updated>2011-04-14T14:24:22-07:00</updated>   
 - <author>  
@@ -77,7 +77,7 @@ You can create an Atom (RSS) feed to an intranet location that contains extensio
   </entry>  
 - <entry>  
   <id>Template_Wizard_239.Microsoft.3b38a7e3-5cbc-4389-a92a-d82tyc2ed592</id>   
-  …  
+  ...  
   </entry>  
   </feed>  
   

docs/extensibility/how-to-manage-a-private-gallery-by-using-registry-settings.md

@@ -40,7 +40,7 @@ If you are an administrator or the developer of an Isolated Shell extension, you
 [$RootPath$\ExtensionManager\Repositories\{UniqueGUID}]  
 @={URI}  (REG_SZ)  
 Disabled=0 | 1 (DWORD)  
-Priority=0 (highest priority) … MaxInt (lowest priority) (DWORD) (uint)  
+Priority=0 (highest priority) ... MaxInt (lowest priority) (DWORD) (uint)  
 Protocol=Atom Feed|Sharepoint (REG_SZ)  
 DisplayName={DisplayName} (REG_SZ)  
 DisplayNameResourceID={ID} (REG_SZ)