Merge pull request #11 from MicrosoftDocs/master

updating

Author: WilliamAntonRohm

.openpublishing.redirection.json

@@ -1594,6 +1594,16 @@
             "redirect_url": "/visualstudio/msbuild/msbuild-glossary",
             "redirect_document_id": false
         },
+        {
+            "source_path": "docs/nodejs/tutorial-nodejs.md",
+            "redirect_url": "/visualstudio/javascript/tutorial-nodejs",
+            "redirect_document_id": false
+        },
+        {
+            "source_path": "docs/nodejs/tutorial-nodejs-with-react-and-jsx.md",
+            "redirect_url": "/visualstudio/javascript/tutorial-nodejs-with-react-and-jsx",
+            "redirect_document_id": false
+        },
         {
             "source_path": "docs/profiling/profiling-tools.md",
             "redirect_url": "/visualstudio/profiling/profiling-feature-tour",
@@ -5715,6 +5725,11 @@
             "source_path": "connected-environment/troubleshooting.md",
             "redirect_url": "/azure/dev-spaces/troubleshooting",
             "redirect_document_id": false
+        },
+        {
+            "source_path": "mac/benefits-vsmac-over-xs.md",
+            "redirect_url": "/visualstudio/mac/",
+            "redirect_document_id": false
         }
 
     ]

docs/code-quality/code-analysis-for-managed-code-overview.md

@@ -23,6 +23,9 @@ Code analysis for managed code analyzes managed assemblies and reports informati
 
 The analysis tool represents the checks it performs during an analysis as warning messages. Warning messages identify any relevant programming and design issues and, when it is possible, supply information about how to fix the problem.
 
+> [!NOTE]
+> Static code analysis is not supported for .NET Core and .NET Standard projects in Visual Studio. If you run code analysis on a .NET Core or .NET Standard project as part of msbuild, you'll see an error similar to **error : CA0055 : Could not identify platform for \<your.dll>**. To analyze code in .NET Core or .NET Standard projects, use [Roslyn analyzers](../code-quality/roslyn-analyzers-overview.md) instead.
+
 ## IDE (integrated development environment) integration
 
 You can run code analysis on your project manually or automatically.

docs/data-tools/bind-wpf-controls-to-a-dataset.md

@@ -234,7 +234,7 @@ Build and run the application. Verify that you can view and update product recor
 
 ## Next steps
 
-After completing this walkthrough, you you might try the following related tasks:
+After completing this walkthrough, you might try the following related tasks:
 
 - Learn how to use the **Data Sources** window in Visual Studio to bind WPF controls to other types of data sources. For more information, see [Bind WPF controls to a WCF data service](../data-tools/bind-wpf-controls-to-a-wcf-data-service.md).
 
@@ -244,4 +244,4 @@ After completing this walkthrough, you you might try the following related tasks
 
 - [Bind WPF controls to data in Visual Studio](../data-tools/bind-wpf-controls-to-data-in-visual-studio.md)
 - [Dataset tools in Visual Studio](../data-tools/dataset-tools-in-visual-studio.md)
-- [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview)
+- [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview)

docs/data-tools/fill-datasets-by-using-tableadapters.md

@@ -100,7 +100,7 @@ TableAdapters use data commands to read to and write from the database. Use the
 When you use a TableAdapter, it effectively performs the same operations with the commands that you would typically perform. For example, when you call the adapter's `Fill` method, the adapter runs the data command in its `SelectCommand` property and uses a data reader (for example, <xref:System.Data.SqlClient.SqlDataReader>) to load the result set into the data table. Similarly, when you call the adapter's `Update` method, it runs the appropriate command (in the `UpdateCommand`, `InsertCommand`, and `DeleteCommand` properties) for each changed record in the data table.
 
 > [!NOTE]
-> If there is enough information in the main query, the `InsertCommand`, `UpdateCommand`, and `DeleteCommand` commands are created by default when the the TableAdapter is generated. If the TableAdapter's main query is more than a single table `SELECT` statement, it's possible the designer won't be able to generate `InsertCommand`, `UpdateCommand`, and `DeleteCommand`. If these commands aren't generated, you might receive an error when running the `TableAdapter.Update` method.
+> If there is enough information in the main query, the `InsertCommand`, `UpdateCommand`, and `DeleteCommand` commands are created by default when the TableAdapter is generated. If the TableAdapter's main query is more than a single table `SELECT` statement, it's possible the designer won't be able to generate `InsertCommand`, `UpdateCommand`, and `DeleteCommand`. If these commands aren't generated, you might receive an error when running the `TableAdapter.Update` method.
 
 ## TableAdapter GenerateDbDirectMethods
 

docs/debugger/debugging-absolute-beginners.md

@@ -35,7 +35,7 @@ It helps to clarify the problem that you ran into before you try to fix it. We e
 
 ## Examine your assumptions
 
-Before you investigate a bug or an error, think of the assumptions that made you expect a certain result. Hidden or unknown assumptions can get in the way of identifying a problem even when you are looking right at the cause of the problem in a debugger. You may have a long list of possible assumptions! Here are are few questions to ask yourself to challenge your assumptions.
+Before you investigate a bug or an error, think of the assumptions that made you expect a certain result. Hidden or unknown assumptions can get in the way of identifying a problem even when you are looking right at the cause of the problem in a debugger. You may have a long list of possible assumptions! Here are a few questions to ask yourself to challenge your assumptions.
 
 * Are you using the right API (that is, the right object, function, method, or property)? An API that you're using might not do what you think it does. (After you examine the API call in the debugger, fixing it may require a trip to the documentation to help identify the correct API.)
 
@@ -316,7 +316,7 @@ When you find the region of code with the problem, use the debugger to investiga
 
 * [Inspect variables](../debugger/view-data-values-in-data-tips-in-the-code-editor.md) and check whether they contain the type of values that they should contain. If you find a bad value, find out where the bad value was set (to find where the value was set, you might need to either restart the debugger, look at the [call stack](../debugger/how-to-use-the-call-stack-window.md), or both).
 
-* Check whether your application is executing the code that you expect. (For example, in the sample application, we expected the code for the switch statement to set the galaxy type to Irregular, but the the app skipped the code due to the typo.)
+* Check whether your application is executing the code that you expect. (For example, in the sample application, we expected the code for the switch statement to set the galaxy type to Irregular, but the app skipped the code due to the typo.)
 
 > [!TIP]
 > You use a debugger to help you find bugs. A debugging tool can find bugs *for you* only if it knows the intent of your code. A tool can only know the intent of your code if you, the developer, express that intent. Writing [unit tests](../test/improve-code-quality.md) is how you do that.