Addressed linter issues

Author: Sergio0694

docs/animations/Offset.md

@@ -124,7 +124,7 @@ You can change the way how the animation interpolates between keyframes by defin
 
     **Sample Output**
 
-    ![Use Case 2 Output](../resources/images/Animations/Offset/Use-Case-1.gif)
+    ![Use Case 1 Output](../resources/images/Animations/Offset/Use-Case-1.gif)
 
 - Use this to create chaining animations with other animations. Visit the [AnimationSet](AnimationSet.md) documentation for more information.
 

docs/brushes/BackdropGammaTransferBrush.md

@@ -1,7 +1,7 @@
 ---
 title: BackdropGammaTransferBrush
 author: michael-hawker
-description: The BackdropBlurBrush is a Brush that blurs whatever is behind it in the application.
+description: The BackdropGammaTransferBrush is a Brush which modifies the color values of whatever is behind it in the application.
 keywords: windows 10, uwp, windows community toolkit, uwp community toolkit, uwp toolkit, brush, backdrop, gamma, color
 ---
 

docs/controls/datagrid_guidance/editing_inputvalidation.md

@@ -15,7 +15,7 @@ The [DataGrid](../datagrid.md) control supports cell and row editing functionali
 <controls:DataGrid BeginningEdit="dg_Editing" CellEditEnding="dg_CellEditEnding" RowEditEnding="dg_RowEditEnding" />
 ```
 
-![Editing](../../resources/images/Controls/DataGrid/editing.png)
+![Sample editing UI](../../resources/images/Controls/DataGrid/editing.png)
 
 A cell-level edit is committed when you move to another cell in the same row. All edits in a row are committed when you press ENTER or move to another row. 
 
@@ -51,7 +51,7 @@ Event | RowEditEnded | Occurs when a row edit has been committed or canceled.
 
 DataGrid control supports input validation through **INotifyDataErrorInfo** in your DataModel or ViewModel. Implement data validation logic by implementing **DataErrorsChangedEventArgs**, **HasErrors** and **GetErrors** methods. The DataGrid control automatically shows the error UI in the editing cell/row when the error conditions are met. 
 
-![Validation](../../resources/images/Controls/DataGrid/validation.png)
+![Sample validation UI](../../resources/images/Controls/DataGrid/validation.png)
 
 See [DataGrid Sample](https://github.com/Microsoft/WindowsCommunityToolkit/tree/master/Microsoft.Toolkit.Uwp.SampleApp/SamplePages/DataGrid) for an example of how to handle input validation in the DataGrid control.
 

docs/controls/datagrid_guidance/keyboard_navigation_selection.md

@@ -54,7 +54,7 @@ The DataGrid control supports single row selection as well as multiple rows sele
 <controls:DataGrid SelectionMode="Extended"/>
 ```
 
-![Selection](../../resources/images/Controls/DataGrid/selection.png)
+![Sample selection UI](../../resources/images/Controls/DataGrid/selection.png)
 
 If the **SelectionMode** property is set to **Extended**, the navigation behavior does not change, but navigating with the keyboard while pressing SHIFT (including CTRL+SHIFT) will modify a multi-row selection. Before navigation starts, the control marks the current row as an anchor row. When you navigate while pressing SHIFT, the selection includes all rows between the anchor row and the current row.
 

docs/controls/datagrid_guidance/rowdetails.md

@@ -9,7 +9,7 @@ keywords: windows 10, uwp, windows community toolkit, windows toolkit, DataGrid,
 
 Each row in the [DataGrid](../datagrid.md) control can be expanded to display a row details section. The row details section is defined by a [DataTemplate](https://docs.microsoft.com/uwp/api/windows.ui.xaml.datatemplate) that specifies the appearance of the section and the data to be displayed.
 
-![RowDetails](../../resources/images/Controls/DataGrid/rowdetails.png)
+![Sample row details UI](../../resources/images/Controls/DataGrid/rowdetails.png)
 
 The row details section can be displayed for selected rows, displayed for all rows, or it can be collapsed. The row details section can also be frozen so that it does not scroll horizontally when the DataGrid is scrolled.
 

docs/controls/datagrid_guidance/styling_formatting_options.md

@@ -23,7 +23,7 @@ You can also change the color of the gridlines using **HorizontalGridLinesBrush*
 <controls:DataGrid GridLinesVisibility="All"/>
 ```
 
-![Gridlines](../../resources/images/Controls/DataGrid/gridlines.png)
+![Sample grid lines UI](../../resources/images/Controls/DataGrid/gridlines.png)
 
 ## 2. Alternating rows
 
@@ -96,7 +96,7 @@ Frozen columns are columns that are always displayed and cannot be scrolled out
 <controls:DataGrid FrozenColumnCount="2"/>
 ```
 
-![FrozenColumns](../../resources/images/Controls/DataGrid/frozencolumns.png)
+![Frozen columns UI](../../resources/images/Controls/DataGrid/frozencolumns.png)
 
 ## 6. Reorder and resize columns
 
@@ -109,7 +109,7 @@ You can allow users to:
 <controls:DataGrid CanUserReorderColumns="True" CanUserResizeColumns="True"/>
 ```
 
-![ResizeColumns](../../resources/images/Controls/DataGrid/resizecolumns.png)
+![Sample resize columns UI](../../resources/images/Controls/DataGrid/resizecolumns.png)
 
 ## See Also
 

docs/controls/wpf-winforms/WebView.md

@@ -544,7 +544,7 @@ End Class
 
 ### There’s *WebBrowser*, *WebView*, and *WebViewControl*. What’s the difference?
 
-When people refer to a “web view” they either refer to the [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2) control in .NET, which uses the legacy Internet Explorer "Trident" (MSHTML) engine, the Universal Windows Platform (UWP) [WebView](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.webview ) which uses the Microsoft Edge (EdgeHTML) engine on some versions of Windows and Trident on others, or the [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol), which is a subset of the UWP WebView available for use in Windows Forms, WPF and other desktop (Win32) applications.
+When people refer to a “web view” they either refer to the [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser) control in .NET, which uses the legacy Internet Explorer "Trident" (MSHTML) engine, the Universal Windows Platform (UWP) [WebView](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.webview ) which uses the Microsoft Edge (EdgeHTML) engine on some versions of Windows and Trident on others, or the [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol), which is a subset of the UWP WebView available for use in Windows Forms, WPF and other desktop (Win32) applications.
 
 ### Is *WebViewControl* available on Windows Server?
 

docs/controls/wpf-winforms/WebViewCompatible.md

@@ -17,10 +17,10 @@ The **WebViewCompatible** control shows web content in your Windows Forms or WPF
 Unlike [WebView](WebView.md), **WebViewCompatible** uses one of two rendering engines to support a broader set of Windows clients:
 
 * On Windows 10 devices, the newer Microsoft Edge rendering engine is used to embed a view that renders richly formatted HTML content from a remote web server, dynamically generated code, or content files.
-* On devices running older versions of Windows, the [System.Windows.Controls.WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2) is used, which provides Internet Explorer engine-based rendering.
+* On devices running older versions of Windows, the [System.Windows.Controls.WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser) is used, which provides Internet Explorer engine-based rendering.
 
 > [!NOTE]
-> The Edge runtime does not at the moment work when the process is elevated as an administrator. Therefore **WebViewCompatible** will fall back to use the [System.Windows.Controls.WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2) when it detects that the process is running as administrator.
+> The Edge runtime does not at the moment work when the process is elevated as an administrator. Therefore **WebViewCompatible** will fall back to use the [System.Windows.Controls.WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser) when it detects that the process is running as administrator.
 
 > [!NOTE]
 > If you have feedback about this control, create a new issue in the [Microsoft.Toolkit.Win32 repo](https://github.com/windows-toolkit/Microsoft.Toolkit.Win32/issues) and leave your comments there. If you prefer to submit your feedback privately, you can send it to XamlIslandsFeedback@microsoft.com. Your insights and scenarios are critically important to us.
@@ -32,7 +32,7 @@ Unlike [WebView](WebView.md), **WebViewCompatible** uses one of two rendering en
 
 The WPF version of this control is located in the **Microsoft.Toolkit.Wpf.UI.Controls** namespace. The Windows Forms version is coming soon, and it will be located in the **Microsoft.Toolkit.Forms.UI.Controls** namespace. You can find additional related types (such as event args classes) in the **Microsoft.Toolkit.Win32.UI.Controls.Interop.WinRT** namespace.
 
-These controls wrap an instance of the [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) class, and they provide a subset of members from that class. The [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) is similar to the [WebView](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.webview) class, but it is designed to run out of process in a desktop application (such as a WPF or Windows Forms application) and it supports a smaller set of members.  Because **WebViewCompatible** wraps [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) (on Windows 10) and [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2) (on older versions of Windows), it provides a simpler subset of common functionality.
+These controls wrap an instance of the [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) class, and they provide a subset of members from that class. The [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) is similar to the [WebView](https://docs.microsoft.com/uwp/api/windows.ui.xaml.controls.webview) class, but it is designed to run out of process in a desktop application (such as a WPF or Windows Forms application) and it supports a smaller set of members.  Because **WebViewCompatible** wraps [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) (on Windows 10) and [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser) (on older versions of Windows), it provides a simpler subset of common functionality.
 
 Unless specified otherwise in this article, the documentation for the [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) class applies to the WPF and Windows Forms **WebView** controls. This article links to reference pages for the UWP [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol) class for more information about most members.
 
@@ -50,7 +50,7 @@ Unless specified otherwise in this article, the documentation for the [WebViewCo
 
 When compared to the UWP **WebView** control, the current release of the WPF and Windows Forms [WebView](WebView.md) controls have some limitations. For the complete list of these limitations, see [Known Issues of the WebView control for Windows Forms and WPF applications](WebView-known-issues.md). 
 
-The **WebViewCompatible** control has further limitations because it exposes a common interface that is a subset of common functionality across the two underlying implementations. On a Windows 10 computer that supports [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol), **WebViewCompatible** has the same limitations as [WebView](WebView.md) as well as further exclusions to the exposed functionality. On a computer running an earlier version of Windows, **WebViewCompatible** will use [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser?view=netframework-4.7.2) and have the same additional interface limitations.
+The **WebViewCompatible** control has further limitations because it exposes a common interface that is a subset of common functionality across the two underlying implementations. On a Windows 10 computer that supports [WebViewControl](https://docs.microsoft.com/uwp/api/windows.web.ui.interop.webviewcontrol), **WebViewCompatible** has the same limitations as [WebView](WebView.md) as well as further exclusions to the exposed functionality. On a computer running an earlier version of Windows, **WebViewCompatible** will use [WebBrowser](https://docs.microsoft.com/dotnet/api/system.windows.controls.webbrowser) and have the same additional interface limitations.
 
 ## Add the WebViewCompatible control to the Visual Studio Toolbox for Windows Forms applications
 

docs/extensions/ScrollViewerExtensions.md

@@ -99,7 +99,7 @@ MiddleClickScrolling allows you to scroll by click middle mouse button (scroll w
 
 ### Sample Output
 
-![MiddleClickScrolling](../resources/images/Extensions/MiddleClickScrolling.gif)
+![Middle click scrolling UI](../resources/images/Extensions/MiddleClickScrolling.gif)
 
 ### Changing Cursor Type