Skip to content

Commit 02de957

Browse files
committed
fix: MD005/list-indent
Inconsistent indentation for list items at the same level
1 parent 79caed1 commit 02de957

14 files changed

+202
-185
lines changed

.markdownlint.json

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,6 @@
33
"MD001": false,
44
"MD002": false,
55
"MD004": false,
6-
"MD005": false,
76
"MD006": false,
87
"MD007": false,
98
"MD009": false,

docs/code-quality/ca2300-do-not-use-insecure-deserializer-binaryformatter.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ This rule finds <xref:System.Runtime.Serialization.Formatters.Binary.BinaryForma
4141
- Protocol Buffers
4242
- Make the serialized data tamper proof. After serialization, cryptographically sign the serialized data. Before deserializing, validate the cryptographic signature. You must protect the cryptographic key from being disclosed, and should design for key rotations.
4343
- Restrict deserialized types. Implement a custom <xref:System.Runtime.Serialization.SerializationBinder?displayProperty=nameWithType>. Before deserializing with <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter>, set the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Binder> property to an instance of your custom <xref:System.Runtime.Serialization.SerializationBinder>. In the overridden <xref:System.Runtime.Serialization.SerializationBinder.BindToType%2A> method, if the type is unexpected then throw an exception.
44-
- If you restrict deserialized types, you may want to disable this rule and enable rules [CA2301](ca2301-do-not-call-binaryformatter-deserialize-without-first-setting-binaryformatter-binder.md) and [CA2302](ca2302-ensure-binaryformatter-binder-is-set-before-calling-binaryformatter-deserialize.md). Enabling rules [CA2301](ca2301-do-not-call-binaryformatter-deserialize-without-first-setting-binaryformatter-binder.md) and [CA2302](ca2302-ensure-binaryformatter-binder-is-set-before-calling-binaryformatter-deserialize.md) will help ensure that the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Binder> property is always set before deserializing.
44+
- If you restrict deserialized types, you may want to disable this rule and enable rules [CA2301](ca2301-do-not-call-binaryformatter-deserialize-without-first-setting-binaryformatter-binder.md) and [CA2302](ca2302-ensure-binaryformatter-binder-is-set-before-calling-binaryformatter-deserialize.md). Enabling rules [CA2301](ca2301-do-not-call-binaryformatter-deserialize-without-first-setting-binaryformatter-binder.md) and [CA2302](ca2302-ensure-binaryformatter-binder-is-set-before-calling-binaryformatter-deserialize.md) will help ensure that the <xref:System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Binder> property is always set before deserializing.
4545

4646
## When to suppress warnings
4747

docs/debugger/run-windows-store-apps-in-the-simulator.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -45,26 +45,26 @@ The Visual Studio simulator for UWP apps is a desktop application that simulates
4545

4646
- ![Simulator two finger target](../debugger/media/simulator_twofinger.png "SIMULATOR_TwoFinger")
4747

48-
The double target icon indicates the location of two fingers on the device screen.
48+
- The double target icon indicates the location of two fingers on the device screen.
4949

5050
- Move the mouse to position the icons over the object on the device screen.
5151

5252
- Rotate the mouse wheel backward or forward to change the simulated distance of the two fingers before you pinch or zoom.
5353

54-
- - ![Pinch, zoom, and rotate targets](../debugger/media/simulator_twofingerengaged.png "SIMULATOR_TwoFingerEngaged")
54+
- ![Pinch, zoom, and rotate targets](../debugger/media/simulator_twofingerengaged.png "SIMULATOR_TwoFingerEngaged")
5555

56-
Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
56+
- Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
5757

5858
- Press the left button and rotate the mouse wheel forward (away from you) to zoom out (zoom).
5959

6060
## Object rotation
6161
The **Touch emulation rotate** button sets the interaction mode to rotation gestures using two fingers.
6262

63-
- - Move the mouse to position the icons over the object on the device screen.
63+
- Move the mouse to position the icons over the object on the device screen.
6464

6565
- Rotate the mouse wheel backward or forward to change the simulated orientation of the two fingers before you rotate the object.
6666

67-
- - Press the left button and rotate the wheel backward (towards you) to rotate the object counter-clockwise. As you rotate the mouse wheel, one of the two target icons rotates around the other to indicate the relative size of the rotation.
67+
- Press the left button and rotate the wheel backward (towards you) to rotate the object counter-clockwise. As you rotate the mouse wheel, one of the two target icons rotates around the other to indicate the relative size of the rotation.
6868

6969
- Press the left button and rotate the mouse wheel forward (away from you) to rotate the object clockwise.
7070

docs/extensibility/walkthrough-publishing-a-visual-studio-extension.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -74,27 +74,27 @@ This article uses a default VSPackage extension, but the steps are valid for eve
7474

7575
* **VSIX ID** is the unique identifier that Visual Studio uses for your extension. This identifier is required if you would like to have your extension auto-updated. This identifier is auto-populated from the *source.extension.vsixmanifest* file.
7676

77-
* **Logo** that is used for your extension. This logo is auto-populated from the *source.extension.vsixmanifest* file if provided.
77+
* **Logo** that is used for your extension. This logo is auto-populated from the *source.extension.vsixmanifest* file if provided.
7878

79-
* **Short description** of what your extension does. This description is auto-populated from the *source.extension.vsixmanifest* file.
79+
* **Short description** of what your extension does. This description is auto-populated from the *source.extension.vsixmanifest* file.
8080

81-
* **Overview** is a good place to include screenshots and detailed information about what your extension does.
81+
* **Overview** is a good place to include screenshots and detailed information about what your extension does.
8282

83-
* **Supported Visual Studio versions** lets you choose which versions of Visual Studio your extension will work on. Your extension is only installed to those versions.
83+
* **Supported Visual Studio versions** lets you choose which versions of Visual Studio your extension will work on. Your extension is only installed to those versions.
8484

85-
* **Supported Visual Studio edition lets you choose which editions of Visual Studio your extension will work on. Your extension is only installed to those editions.
85+
* **Supported Visual Studio edition lets you choose which editions of Visual Studio your extension will work on. Your extension is only installed to those editions.
8686

87-
* **Type**. The most common type of extensions are **Tools**.
87+
* **Type**. The most common type of extensions are **Tools**.
8888

89-
* **Categories**. Pick up to three that are a best fit for your extension.
89+
* **Categories**. Pick up to three that are a best fit for your extension.
9090

91-
* **Tags** are keywords that help users find your extension. Tags can help increase the search relevance of your extensions in the Marketplace.
91+
* **Tags** are keywords that help users find your extension. Tags can help increase the search relevance of your extensions in the Marketplace.
9292

93-
* **Pricing Category** is the cost of your extension.
93+
* **Pricing Category** is the cost of your extension.
9494

95-
* **Source code repository** allows you to share a link to your source code with the community.
95+
* **Source code repository** allows you to share a link to your source code with the community.
9696

97-
* **Allow Q&A for your extension** lets users leave questions on your extension entry page.
97+
* **Allow Q&A for your extension** lets users leave questions on your extension entry page.
9898

9999
9. Click **Save & Upload**. This option takes you back to your publisher manage page. Your extension has not yet been published. To publish your extension, right-click on your extension and select **Make Public**. You can view how your extension will look like on Marketplace by selecting **View Extension**. For acquisition numbers, click on **Reports**. To make changes to your extension, click on **Edit**.
100100

docs/vs-2015/debugger/debug-multithreaded-applications-in-visual-studio.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -85,8 +85,9 @@ A thread is a sequence of instructions to which the operating system allocates p
8585
Examine and work with threads that are running on the GPU during debugging.
8686

8787
## Related Sections
88-
[Using Breakpoints](../debugger/using-breakpoints.md)
89-
- Use breakpoint filters when you want to place a breakpoint on an individual thread.
88+
89+
[Using Breakpoints](../debugger/using-breakpoints.md)
90+
- Use breakpoint filters when you want to place a breakpoint on an individual thread.
9091

9192
- Tracepoints enable you to trace execution of your program without breaking. This can be useful for studying problems such as deadlocks.
9293

docs/vs-2015/debugger/run-windows-store-apps-in-the-simulator.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -50,26 +50,26 @@ The Visual Studio simulator for Windows Store apps is a desktop application that
5050

5151
- ![Simulator two finger target](../debugger/media/simulator-twofinger.png "SIMULATOR_TwoFinger")
5252

53-
The double target icon indicates the location of two fingers on the device screen.
53+
- The double target icon indicates the location of two fingers on the device screen.
5454

5555
- Move the mouse to position the icons over the object on the device screen.
5656

5757
- Rotate the mouse wheel backward or forward to change the simulated distance of the two fingers before you pinch or zoom.
5858

59-
- - ![Pinch, zoom, and rotate targets](../debugger/media/simulator-twofingerengaged.png "SIMULATOR_TwoFingerEngaged")
59+
- ![Pinch, zoom, and rotate targets](../debugger/media/simulator-twofingerengaged.png "SIMULATOR_TwoFingerEngaged")
6060

61-
Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
61+
- Press the left button and rotate the wheel backward (towards you) to zoom in (pinch).
6262

6363
- Press the left button and rotate the mouse wheel forward (away from you) to zoom out (zoom).
6464

6565
## Object rotation
6666
The **Touch emulation rotate** button sets the interaction mode to rotation gestures using two fingers.
6767

68-
- - Move the mouse to position the icons over the object on the device screen.
68+
- Move the mouse to position the icons over the object on the device screen.
6969

7070
- Rotate the mouse wheel backward or forward to change the simulated orientation of the two fingers before you rotate the object.
7171

72-
- - Press the left button and rotate the wheel backward (towards you) to rotate the object counter-clockwise. As you rotate the mouse wheel, one of the two target icons rotates around the other to indicate the relative size of the rotation.
72+
- Press the left button and rotate the wheel backward (towards you) to rotate the object counter-clockwise. As you rotate the mouse wheel, one of the two target icons rotates around the other to indicate the relative size of the rotation.
7373

7474
- Press the left button and rotate the mouse wheel forward (away from you) to rotate the object clockwise.
7575

0 commit comments

Comments
 (0)