Skip to content

Commit 76022e4

Browse files
authored
Fix a couple of typos (#17978)
1 parent 77a5b97 commit 76022e4

2 files changed

Lines changed: 3 additions & 3 deletions

File tree

aspnetcore/fundamentals/routing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -401,7 +401,7 @@ In the following example, a middleware uses the <xref:Microsoft.AspNetCore.Routi
401401

402402
Tokens within `{}` define route parameters that are bound if the route is matched. More than one route parameter can be defined in a route segment, but route parameters must be separated by a literal value. For example, `{controller=Home}{action=Index}` isn't a valid route, since there's no literal value between `{controller}` and `{action}`. Route parameters must have a name and may have additional attributes specified.
403403

404-
Literal text other than route parameters (for example, `{id}`) and the path separator `/` must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URLs path. To match a literal route parameter delimiter `{` or `}`, escape the delimiter by repeating the character. For example `{{` or `}}`.
404+
Literal text other than route parameters (for example, `{id}`) and the path separator `/` must match the text in the URL. Text matching is case-insensitive and based on the decoded representation of the URL's path. To match a literal route parameter delimiter `{` or `}`, escape the delimiter by repeating the character. For example `{{` or `}}`.
405405

406406
Asterisk `*` or double asterisk `**`:
407407

aspnetcore/mvc/controllers/routing.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -467,7 +467,7 @@ In some cases, an HTTP 500 error is returned with ambiguous routes. Use [logging
467467

468468
For convenience, attribute routes support token replacement for reserved route parameters by enclosing a token in one of the following:
469469

470-
* Square braces: `[]`
470+
* Square brackets: `[]`
471471
* Curly braces: `{}`
472472

473473
The tokens `[action]`, `[area]`, and `[controller]` are replaced with the values of the action name, area name, and controller name from the action where the route is defined:
@@ -1212,7 +1212,7 @@ Razor Pages routing and MVC controller routing share an implementation. Informat
12121212

12131213
## Token replacement in route templates ([controller], [action], [area])
12141214

1215-
For convenience, attribute routes support *token replacement* by enclosing a token in square-braces (`[`, `]`). The tokens `[action]`, `[area]`, and `[controller]` are replaced with the values of the action name, area name, and controller name from the action where the route is defined. In the following example, the actions match URL paths as described in the comments:
1215+
For convenience, attribute routes support *token replacement* by enclosing a token in square-brackets (`[`, `]`). The tokens `[action]`, `[area]`, and `[controller]` are replaced with the values of the action name, area name, and controller name from the action where the route is defined. In the following example, the actions match URL paths as described in the comments:
12161216

12171217
[!code-csharp[](routing/samples/2.x/main/Controllers/ProductsController.cs?range=7-11,13-17,20-22)]
12181218

0 commit comments

Comments
 (0)