Update docs/fundamentals/networking/quic/quic-options.md

Co-authored-by: Genevieve Warren <[email protected]>

docs/fundamentals/networking/quic/quic-options.md

@@ -70,7 +70,7 @@ If the connection is inactive for more than the specified <xref:System.Net.Quic.
 
 ### InitialReceiveWindowSizes
 
-<xref:System.Net.Quic.QuicConnectionOptions.InitialReceiveWindowSizes> specify set of values limiting how much data, initially, can be received by the connection and/or the stream. QUIC protocol defines a mechanism to limit how much data can be sent over the individual streams as well as cumulatively for the whole connection ([RFC 9000 - Data Flow Control](https://www.rfc-editor.org/rfc/rfc9000.html#name-data-flow-control)). These limits only apply before the application starts consuming the data. After that, `MsQuic` continually adjusts the receive window's size based on how fast the application reads them. This property is of <xref:System.Net.Quic.QuicReceiveWindowSizes> type, which contains these options:
+<xref:System.Net.Quic.QuicConnectionOptions.InitialReceiveWindowSizes> specifies a set of values limiting how much data, initially, can be received by the connection and/or the stream. QUIC protocol defines a mechanism to limit how much data can be sent over the individual streams as well as cumulatively for the whole connection ([RFC 9000 - Data Flow Control](https://www.rfc-editor.org/rfc/rfc9000.html#name-data-flow-control)). These limits only apply before the application starts consuming the data. After that, `MsQuic` continually adjusts the receive window's size based on how fast the application reads them. This property is of <xref:System.Net.Quic.QuicReceiveWindowSizes> type, which contains these options:
 
 - <xref:System.Net.Quic.QuicReceiveWindowSizes.Connection>: cumulative limit for received data across all streams belonging to this connection.
 - <xref:System.Net.Quic.QuicReceiveWindowSizes.LocallyInitiatedBidirectionalStream>: limit for received data on an outgoing bidirectional stream.