From 8c6a20e7bfadbb27efd2e6a2217ae686cd808e73 Mon Sep 17 00:00:00 2001 From: Mike Kistler Date: Sat, 5 Oct 2024 13:55:48 -0500 Subject: [PATCH] Apply suggestions from PR review Co-authored-by: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> --- aspnetcore/fundamentals/openapi/aspnetcore-openapi.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md b/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md index d1c8b99a4e..559f4fc2b8 100644 --- a/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md +++ b/aspnetcore/fundamentals/openapi/aspnetcore-openapi.md @@ -328,14 +328,13 @@ If an endpoint can return different response types in different scenarios, you c #### Excluding endpoints from the generated document -By default, all endpoints that are defined in an app are documented in the generated OpenAPI file, -but endpoints can be excluded from the document using attributes or extension methods. +By default, all endpoints that are defined in an app are documented in the generated OpenAPI file, but endpoints can be excluded from the document using attributes or extension methods. -The mechanism for specifying an endpoint should be excluded depends on the type of app being developed. +The mechanism for specifying an endpoint that should be excluded depends on the type of app being developed. ##### [Minimal APIs](#tab/minimal-apis) -Minimal APIs support two strategies for excluding a given endpoint from the OpenAPI document, using: +Minimal APIs support two strategies for excluding a given endpoint from the OpenAPI document: * * @@ -355,7 +354,7 @@ app.MapGet("/attributes", In controller-based apps, the attribute can be used to exclude an endpoint from the OpenAPI document. -The following example demonstrates how to exclude an endpoint from the generated OpenAPI document. +The following example demonstrates how to exclude an endpoint from the generated OpenAPI document: ```csharp [HttpGet("/private")]