fix up image tags

Author: gewarren

xml/Microsoft.Win32/FileDialog.xml

@@ -526,7 +526,7 @@ Open and save file dialog boxes have a **Favorite Links** panel on the left side
 
  Each file type that is included in the filter is added as a separate item to the **Files of type:** drop-down list in the <xref:Microsoft.Win32.OpenFileDialog> or <xref:Microsoft.Win32.SaveFileDialog>, as shown in the following figure.
 
- ![Using the FileDialog.Filter in the Open Dialog Box](~/add/media/filedialogfilterfigure1.png "Using the FileDialog.Filter in the Open Dialog Box")
+ ![Using the FileDialog.Filter in the Open Dialog Box](~/add/media/filedialogfilterfigure1.png)
 
  The user can choose a file type from this list to filter by. By default, the first item in the list (for example, the first file type) is selected when the <xref:Microsoft.Win32.OpenFileDialog> or <xref:Microsoft.Win32.SaveFileDialog> is displayed. To specify that another file type to be selected, you set the <xref:Microsoft.Win32.FileDialog.FilterIndex> property before showing the <xref:Microsoft.Win32.OpenFileDialog> or <xref:Microsoft.Win32.SaveFileDialog> (by calling <xref:Microsoft.Win32.CommonDialog.ShowDialog*>).
 

xml/System.ComponentModel/BackgroundWorker.xml

@@ -89,7 +89,7 @@
 ## Examples
  The following code example demonstrates the basics of the <xref:System.ComponentModel.BackgroundWorker> class for executing a time-consuming operation asynchronously. The following illustration shows an example of the output.
 
- ![BackgroundWorker simple example](~/add/media/backgroundworker-simple.png "BackgroundWorker simple example")
+ ![BackgroundWorker simple example](~/add/media/backgroundworker-simple.png)
 
  To try this code, create a Windows Forms application. Add a <xref:System.Windows.Forms.Label> control named `resultLabel` and add two <xref:System.Windows.Forms.Button> controls named `startAsyncButton` and `cancelAsyncButton`. Create <xref:System.Windows.Forms.Control.Click> event handlers for both buttons. From the **Components** tab of the Toolbox, add a <xref:System.ComponentModel.BackgroundWorker> component named `backgroundWorker1`. Create <xref:System.ComponentModel.BackgroundWorker.DoWork>, <xref:System.ComponentModel.BackgroundWorker.ProgressChanged>, and <xref:System.ComponentModel.BackgroundWorker.RunWorkerCompleted> event handlers for the <xref:System.ComponentModel.BackgroundWorker>. In the code for the form, replace the existing code with the following code.
 
@@ -98,7 +98,7 @@
 
  The following code example demonstrates the use of the <xref:System.ComponentModel.BackgroundWorker> class for executing a time-consuming operation asynchronously. The following illustration shows an example of the output.
 
- ![BackgroundWorker Fibonacci example](~/add/media/backgroundworker-fibonacci.png "BackgroundWorker Fibonacci example")
+ ![BackgroundWorker Fibonacci example](~/add/media/backgroundworker-fibonacci.png)
 
  The operation computes the selected Fibonacci number, reports progress updates as the calculation proceeds, and permits a pending calculation to be canceled.
 

xml/System.Device.Location/GeoCoordinateWatcher.xml

@@ -361,7 +361,7 @@
 
  The following diagram represents location coordinates that the location provider (for example, a GPS device) supplies to the computer. P1, in the diagram, represents the location data included in a <xref:System.Device.Location.GeoCoordinateWatcher.PositionChanged> event, and P2, P3, and P4 represent points within the movement threshold. So when the location provider supplies data indicating a location at those points (P1, P2, P3, and P4), no <xref:System.Device.Location.GeoCoordinateWatcher.PositionChanged> events are raised, and <xref:System.Device.Location.GeoCoordinateWatcher.Position*> returns P1. The point P5 is outside of the <xref:System.Device.Location.GeoCoordinateWatcher.MovementThreshold*> distance, so at that point, <xref:System.Device.Location.GeoCoordinateWatcher.Position*> is updated and a <xref:System.Device.Location.GeoCoordinateWatcher.PositionChanged> event is raised.
 
- ![Diagram illustrating MovementThreshold](~/add/media/ndp-movementthreshold.png "Diagram illustrating MovementThreshold")
+ ![Diagram illustrating MovementThreshold](~/add/media/ndp-movementthreshold.png)
 
  ]]></format>
         </remarks>

xml/System.Drawing.Drawing2D/FillMode.xml

@@ -34,29 +34,29 @@
   <Docs>
     <summary>Specifies how the interior of a closed path is filled.</summary>
     <remarks>
-      <format type="text/markdown"><![CDATA[  
-  
-## Remarks  
- An application fills the interior of a path using one of two fill modes: alternate or winding. The mode determines how to fill and clip the interior of a closed figure.  
-  
- The default mode is Alternate. To determine the interiors of closed figures in the alternate mode, draw a line from any arbitrary start point in the path to some point obviously outside the path. If the line crosses an odd number of path segments, the starting point is inside the closed region and is therefore part of the fill or clipping area. An even number of crossings means that the point is not in an area to be filled or clipped. An open figure is filled or clipped by using a line to connect the last point to the first point of the figure.  
-  
- The Winding mode considers the direction of the path segments at each intersection. It adds one for every clockwise intersection, and subtracts one for every counterclockwise intersection. If the result is nonzero, the point is considered inside the fill or clip area. A zero count means that the point lies outside the fill or clip area.  
-  
- A figure is considered clockwise or counterclockwise based on the order in which the segments of the figure are drawn.  
-  
-   
-  
-## Examples  
- The following example creates a path that has one open figure (an arc) and one closed figure (an ellipse). The FillPath method fills the path according to the default fill mode, which is Alternate. The following illustration shows the output of the example code. Note that the path is filled (according to Alternate) as if the open figure were closed by a straight line from its ending point to its starting point.  
-  
- ![Fill Open Path](~/add/media/fillopenpath.png "Fill Open Path")  
-  
- The following example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs> `e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler.  
-  
+      <format type="text/markdown"><![CDATA[
+
+## Remarks
+ An application fills the interior of a path using one of two fill modes: alternate or winding. The mode determines how to fill and clip the interior of a closed figure.
+
+ The default mode is Alternate. To determine the interiors of closed figures in the alternate mode, draw a line from any arbitrary start point in the path to some point obviously outside the path. If the line crosses an odd number of path segments, the starting point is inside the closed region and is therefore part of the fill or clipping area. An even number of crossings means that the point is not in an area to be filled or clipped. An open figure is filled or clipped by using a line to connect the last point to the first point of the figure.
+
+ The Winding mode considers the direction of the path segments at each intersection. It adds one for every clockwise intersection, and subtracts one for every counterclockwise intersection. If the result is nonzero, the point is considered inside the fill or clip area. A zero count means that the point lies outside the fill or clip area.
+
+ A figure is considered clockwise or counterclockwise based on the order in which the segments of the figure are drawn.
+
+
+
+## Examples
+ The following example creates a path that has one open figure (an arc) and one closed figure (an ellipse). The FillPath method fills the path according to the default fill mode, which is Alternate. The following illustration shows the output of the example code. Note that the path is filled (according to Alternate) as if the open figure were closed by a straight line from its ending point to its starting point.
+
+ ![Fill Open Path](~/add/media/fillopenpath.png)
+
+ The following example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs> `e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler.
+
  :::code language="csharp" source="~/snippets/csharp/System.Drawing.Drawing2D/FillMode/Overview/Class1.cs" id="Snippet11":::
- :::code language="vb" source="~/snippets/visualbasic/System.Drawing.Drawing2D/FillMode/Overview/Class1.vb" id="Snippet11":::  
-  
+ :::code language="vb" source="~/snippets/visualbasic/System.Drawing.Drawing2D/FillMode/Overview/Class1.vb" id="Snippet11":::
+
  ]]></format>
     </remarks>
     <related type="Article" href="/dotnet/framework/winforms/advanced/how-to-fill-open-figures">How To: Fill Open Figures</related>

xml/System.Drawing.Drawing2D/HatchBrush.xml

@@ -151,7 +151,7 @@
 ## Remarks
  The following illustration shows an ellipse filled with a horizontal hatch pattern.
 
- ![Hatch Pattern](~/add/media/hatch1.png "Hatch Pattern")
+ ![Hatch Pattern](~/add/media/hatch1.png)
 
 
 

xml/System.Drawing.Drawing2D/LineCap.xml

@@ -39,7 +39,7 @@
 ## Remarks
  You can draw the start or end of a line in one of several shapes called line caps. GDI+ supports several line caps, such as round, square, diamond, and arrowhead. The following illustration shows a line with a round cap and an arrow cap.
 
- ![Pens](~/add/media/pens4.gif "Pens")
+ ![Pens](~/add/media/pens4.gif)
 
 
 

xml/System.Drawing.Imaging/ColorMatrix.xml

@@ -55,13 +55,13 @@
 
  The following matrix multiplication will perform the pair of transformations in the order listed.
 
- ![Recoloring](~/add/media/recoloring01.gif "Recoloring")
+ ![Recoloring](~/add/media/recoloring01.gif)
 
  The elements of a color matrix are indexed (zero-based) by row and then column. For example, the entry in the fifth row and third column of matrix M is denoted by M[4][2].
 
  The 5×5 identity matrix (shown in the following illustration) has 1s on the diagonal and 0s everywhere else. If you multiply a color vector by the identity matrix, the color vector does not change. A convenient way to form the matrix of a color transformation is to start with the identity matrix and make a small change that produces the desired transformation.
 
- ![Recoloring](~/add/media/recoloring02.gif "Recoloring")
+ ![Recoloring](~/add/media/recoloring02.gif)
 
  For a more detailed discussion of matrices and transformations, see [Coordinate Systems and Transformations](/dotnet/framework/winforms/advanced/coordinate-systems-and-transformations).
 
@@ -72,7 +72,7 @@
 
  The following illustration shows the original image on the left and the transformed image on the right.
 
- ![Colors](~/add/media/colortrans1.png "Colors")
+ ![Colors](~/add/media/colortrans1.png)
 
  The code in the following example uses the following steps to perform the recoloring:
 

xml/System.Drawing.Imaging/ImageAttributes.xml

@@ -61,7 +61,7 @@
 
  The following illustration shows the original image on the left and the transformed image on the right.
 
- ![Colors](~/add/media/colortrans1.png "Colors")
+ ![Colors](~/add/media/colortrans1.png)
 
  The code in the example uses the following steps to perform the recoloring:
 

xml/System.Drawing/Graphics.xml

@@ -19645,7 +19645,7 @@ The <see cref="T:System.Drawing.Graphics" /> object has a transform applied othe
 ## Examples
  The following method demonstrates the effects of setting the <xref:System.Drawing.Pen.DashCap*>, <xref:System.Drawing.Pen.DashPattern*>, and <xref:System.Drawing.Graphics.SmoothingMode*> properties. The output of the example is shown in the following illustration.
 
- ![Lines with and without smoothing applied.](~/add/media/gdi-smoothingmode.png "Lines with and without smoothing applied.")
+ ![Lines with and without smoothing applied.](~/add/media/gdi-smoothingmode.png)
 
  This example is designed to be used with Windows Forms. Paste the code into a form and call the `ShowPensAndSmoothingMode` method when handling the form's <xref:System.Windows.Forms.Control.Paint> event, passing `e` as <xref:System.Windows.Forms.PaintEventArgs>.
 
@@ -20302,7 +20302,7 @@ This is a more performant alternative to <xref:System.Drawing.Graphics.Transform
 
  The following illustration shows the output of running the previous code example.
 
- ![Translated and transformed ellipse](~/add/media/ndp-tranlatetransform.png "Translated and transformed ellipse")
+ ![Translated and transformed ellipse](~/add/media/ndp-tranlatetransform.png)
 
  ]]></format>
         </remarks>

xml/System.Drawing/Pen.xml

@@ -980,7 +980,7 @@
 ## Remarks
  A line join is the common area that is formed by two lines whose ends meet or overlap. There are three line join styles: miter, bevel, and round. When you specify a line join style for a <xref:System.Drawing.Pen> object, that join style will be applied to all the connected lines in any <xref:System.Drawing.Drawing2D.GraphicsPath> object drawn using that pen. The following illustration shows the results of the beveled line join example.
 
- ![Pens](~/add/media/pens5.gif "Pens")
+ ![Pens](~/add/media/pens5.gif)