Apply light edits to the attributes chapter

Author: ehuss

reference-dev-guide/src/attributes.md

@@ -2,7 +2,7 @@
 
 Attributes should use the following template. Examples are given for phrasing you *should* use, but you should deviate if the attribute doesn't fit any of the examples or if they get in the way of clarity.
 
-When an attribute (or a new attribute position in the grammar) is added, be sure to update all the "attributes on" sections which list which attributes can be used in various positions.
+When an attribute (or a new attribute position in the grammar) is added, be sure to update all the "attributes on" sections that list which attributes can be used in various positions.
 
 ----
 
@@ -11,7 +11,7 @@ r[PARENT.example]
 ## The `example` attribute
 
 r[PARENT.example.intro]
-The *`example` [attribute][attributes]* ...give a high level description.
+The *`example` [attribute][attributes]* ...give a high-level description.
 
 > [!EXAMPLE]
 > ```rust
@@ -22,7 +22,7 @@ The *`example` [attribute][attributes]* ...give a high level description.
 > ```
 
 r[PARENT.example.syntax]
-Describe the accepted syntax of this attribute. You can either explain that it uses one of the pre-existing grammars like `MetaWord` or define an explicit grammar. If there are different forms, briefly describe the syntax here, and link to the appropriate rules below that explain the behavior of the different forms. Examples:
+Describe the accepted syntax of this attribute. You can either explain that it uses one of the pre-existing grammars, like `MetaWord`, or define an explicit grammar. If there are different forms, briefly describe the syntax here and link to the appropriate rules below that explain the behavior of the different forms. Examples:
 
 ----
 
@@ -50,7 +50,7 @@ The `example` attribute uses the [MetaNameValueStr] syntax. The value in the str
 
 ----
 
-The `example` attribute has these forms:
+The `example` attribute has the following forms:
 
 - [MetaWord]
   > [!EXAMPLE]
@@ -92,7 +92,7 @@ The [MetaNameValueStr] form of the `example` attribute provides a way to specify
 > ```
 
 r[PARENT.example.allowed-positions]
-Explain the valid positions where this attribute may be used.
+Explain the valid positions where this attribute can be used.
 
 See [`check_attr`](https://github.com/rust-lang/rust/blob/HEAD/compiler/rustc_passes/src/check_attr.rs) and [`builtin_attrs.rs`](https://github.com/rust-lang/rust/blob/HEAD/compiler/rustc_feature/src/builtin_attrs.rs) in the compiler. Don't forget that some attributes only work as inner or outer attributes. Examples:
 
@@ -110,15 +110,15 @@ The `example` attribute is allowed anywhere attributes are allowed.
 
 ----
 
-If there are unused attribute warnings, or if rustc is incorrectly accepting some positions, include a note about these.
+If there are unused attribute warnings, or if `rustc` is incorrectly accepting some positions, include a note about these.
 
 > [!NOTE]
 > `rustc` ignores use in other positions but lints against it. This may become an error in the future.
 
 ----
 
 r[PARENT.example.duplicates]
-Explain the behavior if the attribute is specified multiple times on an element. See [`AttributeDuplicates`](https://github.com/rust-lang/rust/blob/40d2563ea200f9327a8cb8b99a0fb82f75a7365c/compiler/rustc_feature/src/builtin_attrs.rs#L143) in the compiler. Examples:
+Explain the behavior when the attribute is specified multiple times on an element. See [`AttributeDuplicates`](https://github.com/rust-lang/rust/blob/40d2563ea200f9327a8cb8b99a0fb82f75a7365c/compiler/rustc_feature/src/builtin_attrs.rs#L143) in the compiler. Examples:
 
 ----
 
@@ -160,7 +160,7 @@ If the `example` attribute is used more than once on an item, then the combinati
 ----
 
 r[PARENT.example.ATTR_NAME]
-If this attribute cannot be used with another attribute, specify each one. Do this on both attributes. Example:
+If this attribute cannot be used with another attribute, specify each conflicting attribute. Do this for both attributes. Example:
 
 ----
 
@@ -169,7 +169,7 @@ The `example` attribute may not be used with the [`foo`] attribute.
 ----
 
 r[PARENT.example.unsafe]
-If this is an `unsafe` attribute, explain the safety conditions it must uphold. If not, don't include this section. Be sure to also update `attributes.safety` when adding a new unsafe attribute. Example:
+If this is an `unsafe` attribute, explain the safety conditions it must uphold. Otherwise, do not include this section. Be sure to also update `attributes.safety` when adding a new unsafe attribute. Example:
 
 ----
 
@@ -178,7 +178,7 @@ The `example` attribute must be marked with [`unsafe`][attributes.safety] becaus
 ----
 
 r[PARENT.example.stdlib]
-This rule explains if the attribute is exported in the standard library. Skip this if it is not. Example:
+This rule explains whether the attribute is exported in the standard library. Skip this section if it is not. Example:
 
 ----
 
@@ -187,4 +187,4 @@ The `example` attribute is exported in the standard library prelude as [`core::p
 ----
 
 r[PARENT.example.foo]
-From here on, add rules explaining all the behaviors of the attribute. If the attribute is very simple, you can just have one rule called ".behavior" to explain its behavior. More complex attributes, such as those with multiple kinds of inputs or different modes should describe each as a separate rule.
+From here on, add rules explaining all the behaviors of the attribute. If the attribute is very simple, you can just have one rule called `.behavior` to explain its behavior. More complex attributes, such as those with multiple kinds of inputs or different modes, should describe each as a separate rule.