Skip to content

Commit

Permalink
Change directive definition wording (#32983)
Browse files Browse the repository at this point in the history
  • Loading branch information
guardrex authored Jul 2, 2024
1 parent eb5818e commit 3c1eebc
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions aspnetcore/blazor/components/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ Developers typically create Razor components from Razor component files (`.razor

Components use [Razor syntax](xref:mvc/views/razor). Two Razor features are extensively used by components, *directives* and *directive attributes*. These are reserved keywords prefixed with `@` that appear in Razor markup:

* [Directives](xref:mvc/views/razor#directives): Change the way component markup is parsed or functions. For example, the [`@page`][9] directive specifies a routable component with a route template and can be reached directly by a user's request in the browser at a specific URL.
* [Directives](xref:mvc/views/razor#directives): Change the way component markup is compiled or functions. For example, the [`@page`][9] directive specifies a routable component with a route template and can be reached directly by a user's request in the browser at a specific URL.

By convention, a component's directives at the top of a component definition (`.razor` file) are placed in a consistent order. For repeated directives, directives are placed alphabetically by namespace or type, except `@using` directives, which have special second-level ordering.

Expand Down Expand Up @@ -87,7 +87,7 @@ Components use [Razor syntax](xref:mvc/views/razor). Two Razor features are exte
...
```

* [Directive attributes](xref:mvc/views/razor#directive-attributes): Change the way a component element is parsed or functions.
* [Directive attributes](xref:mvc/views/razor#directive-attributes): Change the way a component element is compiled or functions.

Example:

Expand Down

0 comments on commit 3c1eebc

Please sign in to comment.