Skip to content

Commit cbc821c

Browse files
authored
Remove extraneous trailing colons (#44153)
1 parent 3692cef commit cbc821c

File tree

4 files changed

+5
-7
lines changed

4 files changed

+5
-7
lines changed

docs/framework/windows-workflow-foundation/samples/suspended-instance-management.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,7 @@
11
---
2-
description: "Learn more about: Suspended Instance Management"
32
title: "Suspended Instance Management"
3+
description: "Learn more about: Suspended Instance Management"
44
ms.date: "03/30/2017"
5-
ms.assetid: f5ca3faa-ba1f-4857-b92c-d927e4b29598
65
---
76
# Suspended Instance Management
87

@@ -58,7 +57,7 @@ The [SuspendedInstanceManagement sample](https://github.com/dotnet/samples/tree/
5857

5958
1. In Visual Studio, run the SampleWorkflowApp project again without debugging by pressing <kbd>Ctrl</kbd>+<kbd>F5</kbd>. Two endpoint addresses will be printed in the console window: one for the application endpoint and then other from the <xref:System.ServiceModel.Activities.WorkflowControlEndpoint>. A workflow instance is then created, and tracking records for that instance will appear in the console window. The workflow instance will throw an exception causing the instance to be suspended and aborted.
6059

61-
2. The command-line utility can then be used to take further action on any of these instances. The syntax for command line arguments is as follows::
60+
2. The command-line utility can then be used to take further action on any of these instances. The syntax for command line arguments is as follows:
6261

6362
`SuspendedInstanceManagement -Command:[CommandName] -Server:[ServerName] -Database:[DatabaseName] -InstanceId:[InstanceId]`
6463

docs/standard/linq/find-element-specific-attribute.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,7 @@ Module Module1
8484
End Module
8585
```
8686

87-
This example produces the following output::
87+
This example produces the following output:
8888

8989
```xml
9090
<aw:Address aw:Type="Billing" xmlns:aw="http://www.adventure-works.com">

docs/standard/linq/valid-content-xelement-xdocument-objects.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,6 @@
22
title: Valid content of XElement and XDocument objects - LINQ to XML
33
description: The XElement and XDocument constructors accept many argument types, including collections returned from queries. There are other constructors and functions for adding XML content.
44
ms.date: 07/20/2015
5-
ms.assetid: 0d253586-2b97-459f-b1a7-f30f38f3ed9f
65
---
76

87
# Valid content of XElement and XDocument objects (LINQ to XML)
@@ -13,7 +12,7 @@ This article describes the valid arguments that can be passed to constructors, a
1312

1413
Queries often evaluate to <xref:System.Collections.Generic.IEnumerable%601> of <xref:System.Xml.Linq.XElement> or <xref:System.Collections.Generic.IEnumerable%601> of <xref:System.Xml.Linq.XAttribute>. You can pass collections of <xref:System.Xml.Linq.XElement> or <xref:System.Xml.Linq.XAttribute> objects to the <xref:System.Xml.Linq.XElement> constructor. That's why it's convenient to pass the results of a query as content into methods and constructors that you use to populate XML trees.
1514

16-
When adding simple content, various types can be passed to this method, including::
15+
When adding simple content, various types can be passed to this method, including:
1716

1817
- <xref:System.String>
1918
- <xref:System.Double>

includes/migration-guide/retargeting/core/allow-unicode-bidirectional-control-characters-uris.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ For applications that target versions of .NET Framework starting with 4.7.2, sup
1414
</runtime>
1515
```
1616

17-
For applications that target earlier versions of the .NET Framework but are running under versions starting with .NET Framework 4.7.2, support for Unicode bidirectional characters is disabled by default. You can enable it by adding the following [AppContextSwitchOverrides](~/docs/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element.md) switch to the `<runtime>` section of the application configuration file::
17+
For applications that target earlier versions of the .NET Framework but are running under versions starting with .NET Framework 4.7.2, support for Unicode bidirectional characters is disabled by default. You can enable it by adding the following [AppContextSwitchOverrides](~/docs/framework/configure-apps/file-schema/runtime/appcontextswitchoverrides-element.md) switch to the `<runtime>` section of the application configuration file:
1818

1919
```xml
2020
<runtime>

0 commit comments

Comments
 (0)