integrate PM tech review feedback

Author: TerryGLee

docs/ide/text-spell-checker.md

@@ -1,7 +1,7 @@
 ---
 title: "Learn about the Spell Checker (Preview)"
 description: Learn how to use the Spell Checker in Visual Studio to correct misspelled words in multiple languages and to customize it to share with your dev team.
-ms.date: 05/04/2023
+ms.date: 05/10/2023
 ms.topic: conceptual
 author: TerryGLee
 ms.author: tglee
@@ -22,7 +22,7 @@ Many of the features in Visual Studio are designed to help you write the code yo
 > [!IMPORTANT]
 > This feature is still in development. It's available now in Visual Studio 2022 version 17.5, but it'll be refined in future releases. For the latest news, see the [**Improving the Spell Checker**](https://devblogs.microsoft.com/visualstudio/improving-the-spell-checker/) post on the [Visual Studio Blog](https://devblogs.microsoft.com/visualstudio/).
 
-Visual Studio automatically toggles on the Spell Checker feature with any C#, C++, or Markdown file. Visual Studio marks any words that it detects as misspelled words. Visual Studio also suggests alternate spellings and helps correct them. The feature even does a contextual rename when those misspellings are identifiers so that your code still compiles.
+The Spell Checker is available for any C#, C++, or Markdown file. When the Spell Checker is enabled, Visual Studio marks any words that it detects as misspelled words. Visual Studio also suggests alternate spellings and helps correct them. The feature even does a contextual rename when those misspellings are identifiers so that your code still compiles.
 
 You can turn the spell checker off or on by using the **Toggle Text Spell Checker** button on the main toolbar, or by selecting **Edit** > **Advanced** > **Toggle Text Spell Checker** command from the menu bar.
 
@@ -40,7 +40,10 @@ You can also choose to ignore the spelling issue. By choosing to ignore the issu
 
 Because C#, C++, and Markdown all use English as the language for their keywords, Visual Studio typically uses the "English (United States)" or "en-us" dictionary for spell checking. Visual Studio checks the instance of Windows for the display language it's using, and if it's not "en-us", it uses that dictionary as well.
 
-Feedback from early users of this feature informed us that developers wanted to know about errors in the documents they were currently working with. In direct response to this feedback, the spell checker scans documents that are open.
+> [!NOTE]
+> C# and C++ also have additional dictonaries for keywords in those languages, which prevents words like ‘namespace’ or ‘alloc’ from being flagged as misspelled words.
+
+Feedback from early users of this feature informed us that developers only want to know about errors in the document they are currently working with. In response to that feedback, the spell checker only scans the document(s) that are active in the editor. In direct response to this feedback, the spell checker scans documents that are open.
 
 The following table shows some of the heuristics that the **Spell Checker** looks at when it scans a code document:
 
@@ -54,7 +57,7 @@ The following table shows some of the heuristics that the **Spell Checker** look
 | btnWorld | World, world | Fragments of three characters or fewer are ignored |
 | helloworld | Helloworld, helloworld | No indicator to identify word boundaries |
 
-Otherwise, Visual Studio considers the word misspelled and flags the token as a spelling error. Visual Studio displays the spelling error with a severity of "Message" in the Error List with a "SPELL" Code.
+If Visual Studio finds a match for the token in any of the dictionaries it's using, the token is considered acceptable and the scan carries on. Otherwise, the token is considered misspelled and Visual Studio flags it as a spelling error.
 
 :::image type="content" source="media/vs-2022/text-spell-checker-error-list-example.png" alt-text="Screenshot of an example of spelling errors in the Error List.":::
 
@@ -72,7 +75,7 @@ Here are some examples and use-case scenarios of the switches you can configure
     ```(Example: = en-us,fr-fr)```
 
     > [!NOTE]
-    > Make sure to install the [language pack](../install/install-visual-studio.md) for any non-default language you're using to prevent Visual Studio from incorrectly flagging words as spelling errors.
+    > Make sure to install the [language pack](../install/install-visual-studio.md) for any language you're using to prevent Visual Studio from incorrectly flagging words as spelling errors.
 
 - Control what Visual Studio should check. In this example, Visual Studio would check identifiers and comments for misspelled words but wouldn’t check inside strings.
 
@@ -90,7 +93,7 @@ Here are some examples and use-case scenarios of the switches you can configure
     ```(Example: = .\exclusion.dic)```
 
     > [!NOTE]
-    > Visual Studio uses the exclusion dictionary specified by the spelling_exclusion_path switch in your .editorconfig file or an "exclusion.dic" file in your `%localappdata%\Microsoft\VisualStudio\<Version>` directory if a switch can’t be found. In either case, the spell-checking APIs require the exclusion file to have "UTF-16 with BOM" encoding to work correctly. 
+    > Visual Studio uses the exclusion dictionary specified by the spelling_exclusion_path switch in your .editorconfig file or an "exclusion.dic" file in your `%localappdata%\Microsoft\VisualStudio\<Version>` directory if a switch can’t be found.  
 
 - Control whether the language-specific exclusion dictionary so use. When set to false, any words specified in the exclusion dictionaries specific to C++ or C# won't be used. The default is true.
 
@@ -99,10 +102,10 @@ Here are some examples and use-case scenarios of the switches you can configure
 
 ## Special case handling
 
-In Visual Studio, some strings aren't recommended for spell-checking. Other strings aren't spell checked or aren't spell checked in their entirety.
+There are a few special behaviors in how Visual Studio checks code for spelling errors that are different from a traditional spell checker that's designed for written text. Some of these behaviors include:
 
-- Strings that include punctuation aren't recommended. For example, `misc.` isn't recommended as it could result in code that won't compile.
-- Backslashes in a string can omit the subsequent character from being spell-checked. For example, `\nhello` won't be flagged as a spelling error because the "n" is omitted and "hello" is a correctly spelled word. 
+- In a string that includes punctuation, for example, 'misc.", Visual Studio won't suggest a correction because punctuation in an identifier might result in code that won't compile.
+- Backslashes in a string will omit the subsequent character from being spell-checked and treat the backslash and subsequent character as a word delimiter. For example, in the string `hello\nworld`, Visual Studio detects the backslash first. Visual Studio treats the `\n` as a word delimiter, which leaves "hello" and "world", each of which are checked individually.
 - Strings that contain URLs such as `https://...` or `mailto:..` won't be spell-checked over the entire string.
 
 ## See also