Apply suggestions from code review

Co-authored-by: Günther Foidl <[email protected]>

Author: Rick-Anderson

aspnetcore/fundamentals/middleware/request-response.md

@@ -70,11 +70,10 @@ These issues are fixable, but the code is becoming progressively more complicate
 
 ## Pipelines
 
-When writing directly to `HttpResponse.BodyWriter`, call `PipeWriter.FlushAsync()` manually to ensure the data is flushed to the underlying response stream. Here's why:
+When writing directly to `HttpResponse.BodyWriter`, call `PipeWriter.FlushAsync()` manually to ensure the data is flushed to the underlying response data structure. Here's why:
 
 * `HttpResponse.BodyWriter` is a `PipeWriter` that buffers data until a flush operation is triggered.
-* Calling `FlushAsync` writes the buffered data to the underlying Stream (`HttpResponse.Body`).
-* 
+* Calling `FlushAsync` writes the buffered data to the underlying network operation
 The following example shows how the same scenario can be handled using a [PipeReader](/dotnet/standard/io/pipelines#pipe):
 
 [!code-csharp[](request-response/samples/3.x/RequestResponseSample/Startup.cs?name=GetListOfStringFromPipe)]