dotnet · gewarren · Nov 2, 2020 · Oct 31, 2020 · Nov 2, 2020 · Nov 2, 2020
diff --git a/docs/visual-basic/developing-apps/creating-and-using-components.md b/docs/visual-basic/developing-apps/creating-and-using-components.md
@@ -7,9 +7,9 @@ ms.assetid: ee6a4156-73f7-4e9b-8e01-c74c4798b65c
 ---
 # Creating and Using Components in Visual Basic
 
-A *component* is a class that implements the <xref:System.ComponentModel.IComponent?displayProperty=nameWithType> interface or that derives directly or indirectly from a class that implements <xref:System.ComponentModel.IComponent>. A .NET Framework component is an object that is reusable, can interact with other objects, and provides control over external resources and design-time support.  
+A *component* is a class that implements the <xref:System.ComponentModel.IComponent?displayProperty=nameWithType> interface or that derives directly or indirectly from a class that implements <xref:System.ComponentModel.IComponent>. A .NET component is an object that is reusable, can interact with other objects, and provides control over external resources and design-time support.  
 
- An important feature of components is that they are designable, which means that a class that is a component can be used in the Visual Studio Integrated Development Environment. A component can be added to the Toolbox, dragged and dropped onto a form, and manipulated on a design surface. Notice that base design-time support for components is built into the .NET Framework; a component developer does not have to do any additional work to take advantage of the base design-time functionality.  
+ An important feature of components is that they are designable, which means that a class that is a component can be used in the Visual Studio Integrated Development Environment. A component can be added to the Toolbox, dragged and dropped onto a form, and manipulated on a design surface. Base design-time support for components is built into .NET. A component developer does not have to do any additional work to take advantage of the base design-time functionality.  
 
  A *control* is similar to a component, as both are designable. However, a control provides a user interface, while a component does not. A control must derive from one of the base control classes: <xref:System.Windows.Forms.Control> or <xref:System.Web.UI.Control>.  
 

diff --git a/...reading-from-and-writing-to-the-registry-using-the-microsoft-win32-namespace.md b/...reading-from-and-writing-to-the-registry-using-the-microsoft-win32-namespace.md
@@ -7,7 +7,7 @@ ms.assetid: 4a0dcce0-c27b-4199-baa8-ee4528da6a56
 ---
 # Reading from and Writing to the Registry Using the Microsoft.Win32 Namespace (Visual Basic)
 
-Although `My.Computer.Registry` should cover your basic needs when programming against the registry, you can also use the <xref:Microsoft.Win32.Registry> and <xref:Microsoft.Win32.RegistryKey> classes in the <xref:Microsoft.Win32> namespace of the .NET Framework.  
+Although `My.Computer.Registry` should cover your basic needs when programming against the registry, you can also use the <xref:Microsoft.Win32.Registry> and <xref:Microsoft.Win32.RegistryKey> classes in the <xref:Microsoft.Win32> namespace of .NET.
 
 ## Keys in the Registry Class  
 

diff --git a/...apps/programming/computer-resources/reading-from-and-writing-to-the-registry.md b/...apps/programming/computer-resources/reading-from-and-writing-to-the-registry.md
@@ -11,7 +11,7 @@ ms.assetid: a13da106-185b-41d7-b23c-416da65e21e4
 
 This topic describes task and conceptual topics that are associated with the registry.  
 
- When programming in Visual Basic, you can choose to access the registry by means of either the functions provided by Visual Basic or the registry classes of the .NET Framework. The registry hosts information from the operating system as well as information from applications hosted on the machine. Working with the registry may compromise security by allowing inappropriate access to system resources or protected information.  
+ When programming in Visual Basic, you can choose to access the registry by means of either the functions provided by Visual Basic or the registry classes of .NET. The registry hosts information from the operating system as well as information from applications hosted on the machine. Working with the registry may compromise security by allowing inappropriate access to system resources or protected information.  
 
 ## In This Section  
 
@@ -25,7 +25,7 @@ This topic describes task and conceptual topics that are associated with the reg
  Describes how to use the `DeleteSubKey` method of the `My.Computer.Registry.CurrentUser` property to delete a registry key.  
 
  [Reading from and Writing to the Registry Using the Microsoft.Win32 Namespace](reading-from-and-writing-to-the-registry-using-the-microsoft-win32-namespace.md)  
- Describes how to use the `Registry` and `RegistryKey` classes of the .NET Framework to access the registry.  
+ Describes how to use the `Registry` and `RegistryKey` classes of .NET to access the registry.  
 
  [Security and the Registry](security-and-the-registry.md)  
  Discusses security issues involving the registry.  

diff --git a/...ng-apps/programming/log-info/walkthrough-filtering-my-application-log-output.md b/...ng-apps/programming/log-info/walkthrough-filtering-my-application-log-output.md
@@ -132,7 +132,7 @@ This table explains the log output shown in the previous example: with the defau
 9. Change the value of the `value` attribute back to "Information".
 
     > [!NOTE]
-    > The `DefaultSwitch` switch setting controls only `My.Application.Log`. It does not change how the .NET Framework <xref:System.Diagnostics.Trace?displayProperty=nameWithType> and <xref:System.Diagnostics.Debug?displayProperty=nameWithType> classes behave.
+    > The `DefaultSwitch` switch setting controls only `My.Application.Log`. It does not change how the .NET <xref:System.Diagnostics.Trace?displayProperty=nameWithType> and <xref:System.Diagnostics.Debug?displayProperty=nameWithType> classes behave.
 
 ## Individual Filtering For My.Application.Log Listeners
 

diff --git a/docs/visual-basic/developing-apps/windows-forms/index.md b/docs/visual-basic/developing-apps/windows-forms/index.md
@@ -22,7 +22,7 @@ You can create Windows Forms and Windows service applications with Visual Studio
 
 ## Building Rich, Interactive User Interfaces
 
-Windows Forms is the smart-client component of the .NET Framework, a set of managed libraries that enable common application tasks such as reading and writing to the file system. Using a development environment like Visual Studio, you can create Windows Forms applications that display information, request input from users, and communicate with remote computers over a network.
+Windows Forms is the smart-client component of the .NET Framework and .NET Core (since .NET Core 3.0). It's a set of managed libraries that enable common application tasks, such as reading and writing to the file system. Using a development environment like Visual Studio, you can create Windows Forms applications that display information, request input from users, and communicate with remote computers over a network.
 
 In Windows Forms, a form is a visual surface on which you display information to the user. You commonly build Windows Forms applications by placing controls on forms and developing responses to user actions, such as mouse clicks or key presses. A *control* is a discrete user interface (UI) element that displays data or accepts data input.
 
@@ -91,7 +91,7 @@ For a full introduction to ClickOnce, see [ClickOnce Security and Deployment](/v
 
 ## Other Controls and Features
 
-There are many other features in Windows Forms that make implementing common tasks fast and easy, such as support for creating dialog boxes, printing, adding Help and documentation, and localizing your application to multiple languages. In addition, Windows Forms relies on the robust security system of the .NET Framework, enabling you to release more secure applications to your customers.
+There are many other features in Windows Forms that make implementing common tasks fast and easy, such as support for creating dialog boxes, printing, adding documentation, and localizing your application to multiple languages. In addition, Windows Forms relies on the robust security system of .NET, enabling you to release more secure applications to your customers.
 
 For step-by-step information about using these features, see the following Help topics: