Fixing typo in RazorPage doc comments
This commit is contained in:
parent
eb7b0d6ae3
commit
99eb8f06ad
|
|
@ -558,13 +558,14 @@ namespace Microsoft.AspNet.Mvc.Razor
|
||||||
/// Invokes <see cref="TextWriter.FlushAsync"/> on <see cref="Output"/> writing out any buffered
|
/// Invokes <see cref="TextWriter.FlushAsync"/> on <see cref="Output"/> writing out any buffered
|
||||||
/// content to the <see cref="HttpResponse.Body"/>.
|
/// content to the <see cref="HttpResponse.Body"/>.
|
||||||
/// </summary>
|
/// </summary>
|
||||||
/// <returns>A<see cref="Task{HtmlString}"/> that represents the asynchronous flush operation and on
|
/// <returns>A <see cref="Task{HtmlString}"/> that represents the asynchronous flush operation and on
|
||||||
/// completion returns a <see cref="HtmlString.Empty"/>.</returns>
|
/// completion returns a <see cref="HtmlString.Empty"/>.</returns>
|
||||||
/// <remarks>The value returned is a token value that allows FlushAsync to work directly in an HTML
|
/// <remarks>The value returned is a token value that allows FlushAsync to work directly in an HTML
|
||||||
/// section. However the value does not represent the rendered content.
|
/// section. However the value does not represent the rendered content.
|
||||||
/// This method also writes out headers, so any modifications to headers must be done before FulshAsync is
|
/// This method also writes out headers, so any modifications to headers must be done before
|
||||||
/// called. For example, call <see cref="SetAntiForgeryCookieAndHeader"/> to send anti-forgery cookie token
|
/// <see cref="FlushAsync"/> is called. For example, call <see cref="SetAntiForgeryCookieAndHeader"/> to send
|
||||||
/// and X-Frame-Options header to client before this method flushes headers out. </remarks>
|
/// anti-forgery cookie token and X-Frame-Options header to client before this method flushes headers out.
|
||||||
|
/// </remarks>
|
||||||
public async Task<HtmlString> FlushAsync()
|
public async Task<HtmlString> FlushAsync()
|
||||||
{
|
{
|
||||||
// If there are active writing scopes then we should throw. Cannot flush content that has the potential to
|
// If there are active writing scopes then we should throw. Cannot flush content that has the potential to
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue