Merge pull request #3170 from MicrosoftDocs/master

10/29 AM Publish

Author: Taojunshen

docs/code-quality/C26415.md

@@ -16,24 +16,32 @@ ms.workload:
   - "multiple"
 ---
 # C26415 SMART_PTR_NOT_NEEDED
+
 "Smart pointer parameter is used only to access contained pointer. Use T* or T& instead."
 
 **C++ Core Guidelines**:
 R.30: Take smart pointers as parameters only to explicitly express lifetime semantics
 
-Using a smart pointer type to pass data to a function indicates that the target function needs to manage the lifetime of the contained object. However, if the function only uses the smart pointer to access the contained object and never actually calls any code which may lead to its deallocation (never affect its lifetime), there is usually no need to complicate the interface with smart pointers. A plain pointer or reference to the contained object should be preferred.
+Using a smart pointer type to pass data to a function indicates that the target function needs to manage the lifetime of the contained object. However, if the function only uses the smart pointer to access the contained object and never actually calls any code that may lead to its deallocation (that is, never affect its lifetime), there is usually no need to complicate the interface with smart pointers. A plain pointer or reference to the contained object is preferred.
 
 ## Remarks
-- This check is a covers majority of scenarios that also causes C26410, C26415, C26417, and C26418. It is better to cleanup SMART_PTR_NOT_NEEDED first and then switch to edge cases for shared or unique pointers. For more focused cleanup this warning can be disabled.
-  - In addition to the standard std::unqiue_pointer and std::shared_pointer templates, this check recognizes user defined types which are likely intended to be smart pointers. Such types are expected to define the following operations:
-  - overloaded dereference or member access operators, that are public and not marked as deleted;
-  - public destructor which is neither deleted nor defaulted. This includes destructors which are explicitly defined empty.
-  - Interpretation of the operations that can affect lifetime of contained objects is quite broad and includes:
-  - any function which accepts pointer or reference parameter to a non-constant smart pointer;
-  - copy or move constructors or assignment operators;
-  - non-constant functions.
-    ## Example
-    cumbersome lifetime management
+
+This check covers a majority of scenarios that also cause C26410, C26415, C26417, and C26418. It is better to clean up SMART_PTR_NOT_NEEDED first and then switch to edge cases for shared or unique pointers. For more focused cleanup, this warning can be disabled.
+
+In addition to the standard std::unqiue_pointer and std::shared_pointer templates, this check recognizes user-defined types that are likely intended to be smart pointers. Such types are expected to define the following operations:
+
+- Overloaded dereference or member access operators that are public and not marked as deleted.
+- Public destructor that's not deleted or defaulted. This includes destructors that are explicitly defined empty.
+
+Interpretation of the operations that can affect the lifetime of contained objects is broad and includes:
+
+- Any function that accepts a pointer or reference parameter to a non-constant smart pointer
+- Copy or move constructors or assignment operators
+- Non-constant functions
+
+## Example
+
+Cumbersome lifetime management.
 
 ```cpp
 bool set_initial_message(
@@ -57,7 +65,8 @@ void pass_message(const message_info &info)
 ```
 
 ## Example
-cumbersome lifetime management - reworked
+
+Cumbersome lifetime management - reworked.
 
 ```cpp
 void set_initial_message(std::shared_ptr<message> m) noexcept
@@ -72,4 +81,4 @@ void pass_message(const message_info &info)
     set_initial_message(m);
     // ...
 }
-```
+```

docs/data-tools/create-a-windows-forms-user-control-that-supports-simple-data-binding.md

@@ -116,7 +116,7 @@ For simple controls that support databinding, implement the <xref:System.Compone
 
 ## Create a data source from your database
 
-This step uses the **Data Source Configuration**wizard to create a data source based on the `Customers` table in the Northwind sample database. You must have access to the Northwind sample database to create the connection. For information on setting up the Northwind sample database, see [How to: Install sample databases](../data-tools/installing-database-systems-tools-and-samples.md).
+This step uses the **Data Source Configuration** wizard to create a data source based on the `Customers` table in the Northwind sample database. You must have access to the Northwind sample database to create the connection. For information on setting up the Northwind sample database, see [How to: Install sample databases](../data-tools/installing-database-systems-tools-and-samples.md).
 
 1.  On the **Data** menu, click **Show Data Sources**.
 

docs/data-tools/save-data-to-a-database-multiple-tables.md

@@ -80,7 +80,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
 
 1.  On the **Data** menu, select **Show Data Sources**.
 
-2.  In the **Data Sources** window, select**Add New Data Source** to start the **Data Source Configuration Wizard**.
+2.  In the **Data Sources** window, select **Add New Data Source** to start the **Data Source Configuration Wizard**.
 
 3.  On the **Choose a Data Source Type** screen, select **Database**, and then select **Next**.
 
@@ -96,7 +96,7 @@ This walkthrough uses SQL Server Express LocalDB and the Northwind sample databa
 
 6.  On the **Save connection string to the Application Configuration file**, select **Next**.
 
-7.  On the **Choose your Database Objects**screen, expand the **Tables** node.
+7.  On the **Choose your Database Objects** screen, expand the **Tables** node.
 
 8.  Select the **Customers** and **Orders** tables, and then select **Finish**.
 

docs/debugger/debug-interface-access/idiaenumdebugstreams-next.md

@@ -30,7 +30,7 @@ HRESULT Next ( 
 
 #### Parameters  
  celt  
- [in] **T**he number of debug streams in the enumerator to be retrieved.  
+ [in] The number of debug streams in the enumerator to be retrieved.  
 
  rgelt  
  [out] Returns an array of [IDiaEnumDebugStreamData](../../debugger/debug-interface-access/idiaenumdebugstreamdata.md) objects that represents the debug streams being retrieved.  

docs/debugger/diagnose-problems-after-deployment.md

@@ -38,7 +38,7 @@ To diagnose issues in your ASP.NET web app after deployment by using IntelliTrac
 
 Visual Studio 2017 does not include the *BuildInfo.config* file, which was deprecated and then removed. To debug ASP.NET web apps after deployment, use one of the following methods:
 
-* For deployment to Azure, use [Application Insights](https://docs.microsoft.com/en-us/azure/application-insights/).
+* For deployment to Azure, use [Application Insights](https://docs.microsoft.com/azure/application-insights/).
 
 * If you need to use IntelliTrace, open the project in Visual Studio and load the symbol files from the matching build. You can load symbol files from the **Modules** window or by configuring symbols in **Tools** > **Options** > **Debugging** > **Symbols**.
 

docs/debugger/how-to-apply-edits-in-break-mode-with-edit-and-continue.md

@@ -42,7 +42,7 @@ For limitations on using Edit and Continue while debugging, see [Supported Code
 
          -or-  
 
-    -   When an exception occurs, choose **Enable Editing** on the**Exception Assistant**.  
+    -   When an exception occurs, choose **Enable Editing** on the **Exception Assistant**.  
 
 2.  Make any desired and supported code changes.  
 

docs/debugger/how-to-debug-dotnet-framework-source.md

@@ -20,7 +20,7 @@ To debug .NET Framework source, you must have access to debugging symbols for th
 
 ### To enable .NET Framework source debugging  
 
-1.  On the **Tools** menu, click **Option**s.  
+1.  On the **Tools** menu, click **Options**.  
 
 2.  In the **Options** dialog box, click the **Debugging** category.  
 

docs/debugger/how-to-use-the-threads-window.md

@@ -31,7 +31,7 @@ To begin this tutorial, you need a multithreaded application project. Follow the
 
      The **New Project** dialog box appears.  
 
-2.  In the **Project Type**s box, click the language of your choice: **Visual Basic**, **Visual C#**, or **Visual C++**.  
+2.  In the **Project Types** box, click the language of your choice: **Visual Basic**, **Visual C#**, or **Visual C++**.  
 
 3.  Under **Windows Desktop**, choose **Console App**.  
 

docs/debugger/mfc-debugging-techniques.md

@@ -434,7 +434,7 @@ pMyPerson->Dump( afxDump );
 
    4.  In the **Copy Settings from** list, choose **Release**.  
 
-   5.  Click **OK** to close the **New Project Configuration**dialog box.  
+   5.  Click **OK** to close the **New Project Configuration** dialog box.  
 
    6.  Close the **Configuration Manager** dialog box.  
 

docs/extensibility/binding-keyboard-shortcuts-to-menu-items.md

@@ -39,7 +39,7 @@ To bind a keyboard shortcut to a custom menu command, just add an entry to the *
 4. Try different combinations of keys until you find one that is not mapped.  
 
    > [!NOTE]
-   >  Keyboard shortcuts that use **Alt** may open a menu and not directly execute a command. Therefore, the **Shorcut currently used by** box may be blank when you type a shortcut that includes **Alt**. You can verify that the shortcut does not open a menu by closing the **Options** dialog box and then pressing the keys.  
+   >  Keyboard shortcuts that use **Alt** may open a menu and not directly execute a command. Therefore, the **Shortcut currently used by** box may be blank when you type a shortcut that includes **Alt**. You can verify that the shortcut does not open a menu by closing the **Options** dialog box and then pressing the keys.  
   
    The following procedure assumes that you have an existing VSPackage with a menu command. If you need help doing that, take a look at [Create an extension with a menu command](../extensibility/creating-an-extension-with-a-menu-command.md).  
 
@@ -72,7 +72,7 @@ To bind a keyboard shortcut to a custom menu command, just add an entry to the *
 
    In most situations, **Shift** should not be used without a second modifier because pressing it already causes most alphanumeric keys to type an uppercase letter or a symbol.  
 
-   Virtual-key codes let you access special keys that do not have a character associated with them, for example, function keys and the **Backspace** key. For more information, see [Virtual-key codes](https://docs.microsoft.com/en-us/windows/desktop/inputdev/virtual-key-codes).  
+   Virtual-key codes let you access special keys that do not have a character associated with them, for example, function keys and the **Backspace** key. For more information, see [Virtual-key codes](https://docs.microsoft.com/windows/desktop/inputdev/virtual-key-codes).  
 
    To make the command available in the Visual Studio editor, set the `editor` attribute to `guidVSStd97`.  
 

docs/extensibility/internals/creating-project-instances-by-using-project-factories.md

@@ -22,8 +22,6 @@ Project types in [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] us
 
  You can implement the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory> interface in a class in your project. Typically, it resides in its own module.  
 
- For an example of an implementation of the `IVsProjectFactory` interface, see *PrjFac.cpp*, which is contained in the [Basic project](https://www.microsoft.com/download/details.aspx?id=55984) sample directory.  
-  
  Projects that support being aggregated by an owner must persist an owner key in their project file. When the <xref:Microsoft.VisualStudio.Shell.Interop.IVsProjectFactory.CreateProject%2A> method is called on a project with an owner key, the owned project converts its owner key to a project factory GUID then calls the `CreateProject` method on this project factory to do the actual creation.  
 
 ## Create an owned project  

docs/extensibility/internals/guids-and-ids-of-visual-studio-commands.md

@@ -51,7 +51,7 @@ The GUID and ID values of the commands included in the Visual Studio integrated
 
 -   Menu items that include an underlined character, such as the **Print** command on the **File** menu, in which the *P* is underlined.  
 
-     Characters that are preceded by the ampersand (&) character in menu item names are displayed as underlined. However, *.vsct* files are written in XML, which uses the ampersand (&) character to indicate special characters and requires that an ampersand to be displayed must be spelled out as *&*. Therefore, in a *.vsct* file, the **P**rint command appears as *&Print*.  
+     Characters that are preceded by the ampersand (&) character in menu item names are displayed as underlined. However, *.vsct* files are written in XML, which uses the ampersand (&) character to indicate special characters and requires that an ampersand to be displayed must be spelled out as *&*. Therefore, in a *.vsct* file, the **Print** command appears as *&Print*.  
 
 -   Commands that have dynamic text, such as **Save** \<Current Filename\>, and dynamically generated menu items, such as the items on the **Recent Files** list.  
 

docs/extensibility/internals/wizard-interface-idtwizard.md

@@ -31,7 +31,7 @@ STDMETHOD(Execute)(THIS_
    );  
 ```  
 
- The start mechanism is similar for both the **New Project** and **Add New Item**wizards. To start either, you call the <xref:EnvDTE.IDTWizard> interface defined in Dteinternal.h. The only difference is the set of context and custom parameters that are passed to the interface when the interface is called.  
+ The start mechanism is similar for both the **New Project** and **Add New Item** wizards. To start either, you call the <xref:EnvDTE.IDTWizard> interface defined in Dteinternal.h. The only difference is the set of context and custom parameters that are passed to the interface when the interface is called.  
 
  The following information describes the <xref:EnvDTE.IDTWizard> interface that wizards must implement to work in the [!INCLUDE[vsprvs](../../code-quality/includes/vsprvs_md.md)] IDE. The IDE calls the <xref:EnvDTE.IDTWizard.Execute%2A> method on the wizard, passing it the following:  
 

docs/ide/dotfuscator/capabilities.md

@@ -60,7 +60,7 @@ Many of these same methods may also be used to enforce [end-of-life deadlines][s
 
 <!-- Copyright © 2017 PreEmptive Solutions, LLC -->
 
-[assemblies]:  https://docs.microsoft.com/en-us/dotnet/standard/assembly-format
+[assemblies]:  https://docs.microsoft.com/dotnet/standard/assembly-format
 [uwp]:  https://www.preemptive.com/blog/article/856-uwp-applications-in-dotfuscator-ce/91-dotfuscator-ce
 [xamarin]:  https://www.preemptive.com/obfuscating-xamarin-with-dotfuscator
 

docs/ide/dotfuscator/index.md

@@ -79,7 +79,7 @@ See [the full Dotfuscator CE User Guide at preemptive.com][full] for detailed us
 
 <!-- Copyright © 2017 PreEmptive Solutions, LLC -->
 
-[assemblies]:  https://docs.microsoft.com/en-us/dotnet/standard/assembly-format
+[assemblies]:  https://docs.microsoft.com/dotnet/standard/assembly-format
 [software-protection]:  https://www.preemptive.com/software-protection
 [obfuscation]:  https://www.preemptive.com/obfuscation
 [app-protection]:  https://www.preemptive.com/application-protection

docs/ide/find-code-changes-and-other-history-with-codelens.md

@@ -121,7 +121,7 @@ You can find out how many people changed your code and how many changes were mad
 
 ### Find when your code was branched
 
-To find when your code was branched, navigate to your code in the child branch. Then, select the **changes** indicator or press**Alt**+**6**:
+To find when your code was branched, navigate to your code in the child branch. Then, select the **changes** indicator or press **Alt**+**6**:
 
 ![CodeLens: Find when your code was branched](../ide/media/codelens-first-branch.png)
 
@@ -291,7 +291,7 @@ To use the keyboard:
 
 4. Press **Tab** to go to the **Show settings for** list, and then press **Down Arrow** to select **CodeLens**.
 
-### Q: Can I move the CodeLens `head`s-up display?
+### Q: Can I move the CodeLens heads-up display?
 
 **A:** Yes, choose ![Dock icon](../ide/media/codelensdockwindow.png) to dock CodeLens as a window.
 

docs/ide/how-to-track-your-code-by-customizing-the-scrollbar.md

@@ -4,8 +4,6 @@ ms.date: 09/25/2018
 ms.prod: visual-studio-dev15
 ms.technology: vs-ide-general
 ms.topic: conceptual
-f1_keywords:
-  - "VS.ToolsOptionsPages.Text_Editor.All_Languages.Scroll_Bars"
 author: gewarren
 ms.author: gewarren
 manager: douge

docs/ide/quickstart-python.md

@@ -1,7 +1,7 @@
 ---
 title: "Quickstart: use Visual Studio to create a Python web app"
 description: In this quickstart, you use Visual Studio and the Flask framework to build a simple web app in Python.
-ms.date: 06/27/2018
+ms.date: 10/29/2018
 ms.prod: visual-studio-dev15
 ms.prod: visual-studio-dev15
 ms.technology: vs-python

docs/ide/reference/build-events-dialog-box-visual-basic.md

@@ -20,24 +20,26 @@ ms.workload:
   - "multiple"
 ---
 # Build Events Dialog Box (Visual Basic)
+
 Use the **Build Events** dialog box to specify build configuration instructions. You can also specify the conditions under which any pre-build or post-build events are run. For more information, see [How to: Specify Build Events (Visual Basic)](../../ide/how-to-specify-build-events-visual-basic.md).
 
- **Pre-build event command line**
- Specifies any commands to execute before the build starts. To type long commands, click **Edit Pre-build** to display the [Pre-build Event/Post-build Event Command Line Dialog Box](../../ide/reference/pre-build-event-post-build-event-command-line-dialog-box.md).
+**Pre-build event command line**
+
+Specifies any commands to execute before the build starts. To type long commands, click **Edit Pre-build** to display the [Pre-build Event/Post-build Event Command Line Dialog Box](../../ide/reference/pre-build-event-post-build-event-command-line-dialog-box.md).
 
 > [!NOTE]
 > Pre-build events do not run if the project is up-to-date and no build is triggered.
 
+**Post-build event command line**
 
- **Post-build event command line**
- Specifies any commands to execute after the build ends. To type long commands, click **Edit Post-build** to display the **Pre-build Event/Post-build Event Command Line d**ialog box.
+Specifies any commands to execute after the build ends. To type long commands, click **Edit Post-build** to display the **Pre-build Event/Post-build Event Command Line** dialog box.
 
 > [!NOTE]
 > Add a `call` statement before all post-build commands that run .bat files. For example, `call C:\MyFile.bat` or `call C:\MyFile.bat call C:\MyFile2.bat`.
 
+**Run the post-build event**
 
- **Run the post-build event**
- Specifies the conditions for the post-build event to run, as shown in the following table.
+Specifies the conditions for the post-build event to run, as shown in the following table.
 
 |Option|Result|
 |------------|------------|

docs/ide/reference/fonts-and-colors-environment-options-dialog-box.md

@@ -141,7 +141,7 @@ Lists the items for which you can modify the foreground and background color.
 |**Keyword**|Keywords for the given language that are reserved. For example: class and namespace.|
 |**Memory Address**|The color of text used to display the address column inside the **Memory** window.|
 |**Memory Changed**|The color of text used to display changed data inside the **Memory** window.|
-|**Memory Data**|The color of text used to display data inside the M**emory** window.|
+|**Memory Data**|The color of text used to display data inside the **Memory** window.|
 |**Memory Unreadable**|The color of text used to display unreadable memory areas within the **Memory** window.|
 |**Number**|A number in code that represents an actual numeric value.|
 |**Operator**|Operators such as +, -, and !=.|