Apply suggestions from code review

Co-Authored-By: Ron Petrusha <ronpet@microsoft.com>

Author: nxtn

docs/framework/winforms/controls/controls-to-use-on-windows-forms.md

@@ -225,7 +225,7 @@ The following is an alphabetic list of controls and components that can be used
  Provides links to step-by-step topics, recommendations for which kind of control to create, and other information about creating your own control.  
 
  [Controls and Programmable Objects Compared in Various Languages and Libraries](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/0061wezk(v=vs.100))  
- Provides a table that maps controls in Visual Basic 6.0 to the corresponding control in Visual Basic 2005. Note that controls are now classes in the .NET Framework.  
+ Provides a table that maps controls in Visual Basic 6.0 to the corresponding control in Visual Basic .NET. Note that controls are now classes in the .NET Framework.  
 
  [How to: Add ActiveX Controls to Windows Forms](how-to-add-activex-controls-to-windows-forms.md)  
  Describes how to use ActiveX controls on Windows Forms.

docs/visual-basic/programming-guide/language-features/objects-and-classes/object-lifetime-how-objects-are-created-and-destroyed.md

@@ -54,7 +54,7 @@ An instance of a class, an object, is created by using the `New` keyword. Initia
   
  The `Finalize` destructor is a protected method that can be called only from the class it belongs to, or from derived classes. The system calls `Finalize` automatically when an object is destroyed, so you should not explicitly call `Finalize` from outside of a derived class's `Finalize` implementation.  
 
- Unlike `Class_Terminate`, which executes as soon as an object is set to nothing, there is usually a delay between when an object loses scope and when Visual Basic calls the `Finalize` destructor. Visual Basic 2005 and later versions allow for a second kind of destructor, <xref:System.IDisposable.Dispose%2A>, which can be explicitly called at any time to immediately release resources.  
+ Unlike `Class_Terminate`, which executes as soon as an object is set to nothing, there is usually a delay between when an object loses scope and when Visual Basic calls the `Finalize` destructor. Visual Basic .NET allows for a second kind of destructor, <xref:System.IDisposable.Dispose%2A?displayProperty=nameWithType>, which can be explicitly called at any time to immediately release resources.  
 
 > [!NOTE]
 >  A `Finalize` destructor should not throw exceptions, because they cannot be handled by the application and can cause the application to terminate.