Skip to content

Commit 068437d

Browse files
CopilotMihaZupan
andcommitted
Remove trailing whitespace from documentation
Co-authored-by: MihaZupan <[email protected]>
1 parent 7a239c8 commit 068437d

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

xml/System.Net.Http/MultipartContent.xml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -53,11 +53,11 @@
5353
<Docs>
5454
<summary>Provides a collection of <see cref="T:System.Net.Http.HttpContent" /> objects that get serialized using the multipart/* content type specification.</summary>
5555
<remarks>
56-
<format type="text/markdown"><![CDATA[
57-
58-
## Remarks
59-
According to RFC 1341 (MIME) 7.2 and its successors, multipart messages must contain one or more body parts. When a <xref:System.Net.Http.MultipartContent> instance with zero parts is serialized, it's written as a single dummy empty part with no content headers or message body. This ensures compliance with the RFC requirement while maintaining backward compatibility. However, other HTTP clients might not interpret this message as a multipart content with zero parts, so it's recommended to add at least one part before serializing.
60-
56+
<format type="text/markdown"><![CDATA[
57+
58+
## Remarks
59+
According to RFC 1341 (MIME) 7.2 and its successors, multipart messages must contain one or more body parts. When a <xref:System.Net.Http.MultipartContent> instance with zero parts is serialized, it's written as a single dummy empty part with no content headers or message body. This ensures compliance with the RFC requirement while maintaining backward compatibility. However, other HTTP clients might not interpret this message as a multipart content with zero parts, so it's recommended to add at least one part before serializing.
60+
6161
]]></format>
6262
</remarks>
6363
</Docs>

0 commit comments

Comments
 (0)