XML code blocks

docs/framework/migration-guide/mitigation-png-frames-in-icon-objects.md

@@ -23,7 +23,7 @@ Starting with the .NET Framework 4.6, the <xref:System.Drawing.Icon.ToBitmap%2A?
 
 ```xml  
 <AppContextSwitchOverrides
-      value="Switch.System.Drawing.DontSupportPngFramesInIcons=true;previous key=previous value" />
+      value="Switch.System.Drawing.DontSupportPngFramesInIcons=true;previous key=previous-value" />
 ```
 
 ## See also

docs/framework/wcf/simplified-configuration.md

@@ -14,8 +14,8 @@ Configuring Windows Communication Foundation (WCF) services can be a complex tas
   <behaviors>  
     <serviceBehaviors>  
       <behavior name="MyServiceBehavior">  
-        <serviceMetadata httpGetEnabled="true">  
-        <serviceDebug includeExceptionDetailInFaults="false">  
+        <serviceMetadata httpGetEnabled="true" />  
+        <serviceDebug includeExceptionDetailInFaults="false" />  
       </behavior>  
     </serviceBehaviors>  
   </behaviors>  

docs/framework/wcf/troubleshooting-the-getting-started-tutorial.md

@@ -87,7 +87,9 @@ To turn off security:
 - For the client, in the configuration file, update the **\<security>** element under the **\<binding>** element as follows:  
 
     ```xml
-    <binding name="WSHttpBinding_ICalculator" security mode="None" />
+    <binding name="WSHttpBinding_ICalculator">
+      <security mode="None" />
+    </binding
     ```  
 
 ## See also  

docs/framework/whats-new/index.md

@@ -421,7 +421,7 @@ You can add SameSite for <xref:System.Web.Security.FormsAuthentication> and <xre
       <forms cookieSameSite="Lax">
          <!-- ...   -->
       </forms>
-   <authentication />
+   </authentication>
    <sessionState cookieSameSite="Lax"></sessionState>
 </system.web>
 ```
@@ -494,7 +494,7 @@ The basic flow of enclave-based Always Encrypted is:
 Starting with .NET Framework 4.7.2, a diagnostic assistant can locate the <xref:System.Windows.Xps.Packaging.IXpsFixedPageReader.ResourceDictionaries> that have been created from a given source Uri. (This feature is for use by diagnostic assistants, not by production applications.) A diagnostic assistant such as Visual Studio’s “Edit-and-Continue” facility lets its user edit a ResourceDictionary with the intent that the changes be applied to the running application. One step in achieving this is finding all the ResourceDictionaries that the running application has created from the dictionary that’s being edited. For example, an application can declare a ResourceDictionary whose content is copied from a given source URI:
 
 ```xml
-<ResourceDictionary Source="MyRD.xaml">
+<ResourceDictionary Source="MyRD.xaml" />
 ```
 
 A diagnostic assistant that edits the original markup in *MyRD.xaml* can use the new feature to locate the dictionary. The feature is implemented by a new static method, <xref:System.Windows.Diagnostics.ResourceDictionaryDiagnostics.GetResourceDictionariesForSource%2A?displayProperty=nameWithType>. The diagnostic assistant calls the new method using an absolute Uri that identifies the original markup, as illustrated by the following code:

docs/framework/whats-new/whats-new-in-accessibility.md

@@ -562,7 +562,7 @@ Starting with .NET Framework 4.7.1, various WinForms controls offer improved re
 
 ```xml
 <!-- Windows 10 -->
-<supportedOS Id=”{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}” />
+<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />
 ```
 
 Some examples of high contrast changes include:

docs/framework/windows-workflow-foundation/configuring-tracking-for-a-workflow.md

@@ -196,13 +196,13 @@ If events need to be written to a specific application log, follow these steps t
 3. Change the GUID in the manifest file to the new GUID.
 
     ```xml
-    <provider name="Microsoft-Windows-Application Server-Applications" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}"
+    <provider name="Microsoft-Windows-Application Server-Applications" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}" />
     ```
 
 4. Change the provider name if you do not want to uninstall the default provider.
 
     ```xml
-    <provider name="Microsoft-Windows-Application Server-Applications" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}"
+    <provider name="Microsoft-Windows-Application Server-Applications" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}" />
     ```
 
 5. If you changed the provider name in the previous step, change the channel names in the manifest file to the new provider name.
@@ -242,7 +242,7 @@ If events need to be written to a specific application log, follow these steps t
     6. Change the resource and message dll name in the manifest file from `Microsoft.Windows.ApplicationServer.Applications.Provider1.man` to the new dll name.
 
         ```xml
-        <provider name="Microsoft-Windows-Application Server-Applications_Provider1" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}" symbol="Microsoft_Windows_ApplicationServer_ApplicationEvents" resourceFileName="<dll directory>\Microsoft.Windows.ApplicationServer.Applications_Provider1.dll" messageFileName="<dll directory>\Microsoft.Windows.ApplicationServer.Applications_Provider1.dll">
+        <provider name="Microsoft-Windows-Application Server-Applications_Provider1" guid="{2720e974-9fe9-477a-bb60-81fe3bf91eec}" symbol="Microsoft_Windows_ApplicationServer_ApplicationEvents" resourceFileName="<dll directory>\Microsoft.Windows.ApplicationServer.Applications_Provider1.dll" messageFileName="<dll directory>\Microsoft.Windows.ApplicationServer.Applications_Provider1.dll" />
         ```
 
     7. Use [wevtutil](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732848(v=ws.10)) to register the manifest.

docs/framework/windows-workflow-foundation/flowchart-workflows.md

@@ -40,7 +40,7 @@ To model a basic sequence in which two activities execute in turn, the `FlowStep
     </Assign>
     <FlowStep.Next>
       <FlowStep>
-        <WriteLine Text="["Hello, " & result]"/>
+        <WriteLine Text="Hello, " & [result]/>
       </FlowStep>
     </FlowStep.Next>
   </FlowStep>