Fix various spelling and format errors

Author: ehuss

src/attributes/codegen.md

@@ -21,7 +21,7 @@ have no effect on a trait function without a body.
 
 ### The `inline` attribute
 
-r[attributes.codgen.inline]
+r[attributes.codegen.inline]
 
 r[attributes.codegen.inline.intro]
 The *`inline` [attribute]* suggests that a copy of the attributed function
@@ -46,7 +46,7 @@ There are three ways to use the inline attribute:
 
 ### The `cold` attribute
 
-r[attribute.codegen.cold]
+r[attributes.codegen.cold]
 
 The *`cold` [attribute]* suggests that the attributed function is unlikely to
 be called.
@@ -93,13 +93,13 @@ be used with a `target_feature` attribute.
 
 ### Available features
 
-r[attributes.codegen.target_features.availability]
+r[attributes.codegen.target_feature.availability]
 
 The following is a list of the available feature names.
 
 #### `x86` or `x86_64`
 
-r[attributes.codegen.target_features.x86]
+r[attributes.codegen.target_feature.x86]
 
 Executing code with unsupported features is undefined behavior on this platform.
 Hence this platform requires that `#[target_feature]` is only applied to [`unsafe`
@@ -482,7 +482,7 @@ r[attributes.codegen.instruction_set]
 r[attributes.codegen.instruction_set.restriction]
 The *`instruction_set` [attribute]* may be applied to a function to control which instruction set the function will be generated for.
 
-r[attributes.codegen.instruction_set.behaviour]
+r[attributes.codegen.instruction_set.behavior]
 This allows mixing more than one instruction set in a single program on CPU architectures that support it.
 
 r[attributes.codegen.instruction_set.syntax]

src/attributes/diagnostics.md

@@ -499,7 +499,7 @@ The following keys have the given meaning:
 * `label` --- The text for the label shown inline in the broken code in the error message.
 * `note` --- Provides additional notes.
 
-r[attributes.diagnostic.on_unimplemented-note-repetition]
+r[attributes.diagnostic.on_unimplemented.note-repetition]
 The `note` option can appear several times, which results in several note messages being emitted.
 
 r[attributes.diagnostic.on_unimplemented.repetition]
@@ -509,18 +509,18 @@ r[attributes.diagnostic.on_unimplemented.warnings]
 Any other occurrence generates an lint warning.
 For any other non-existing option a lint-warning is generated.
 
-r[attributes.diagnostic.format-string]
+r[attributes.diagnostic.on_unimplemented.format-string]
 All three options accept a string as an argument, interpreted using the same formatting as a [`std::fmt`] string.
 
-r[attributes.diagnostic.format-parameters]
+r[attributes.diagnostic.on_unimplemented.format-parameters]
 Format parameters with the given named parameter will be replaced with the following text:
 * `{Self}` --- The name of the type implementing the trait.
 * `{` *GenericParameterName* `}` --- The name of the generic argument's type for the given generic parameter.
 
-r[attributes.diagnostic.invalid-formats]
+r[attributes.diagnostic.on_unimplemented.invalid-formats]
 Any other format parameter will generate a warning, but will otherwise be included in the string as-is.
 
-r[attributes.diagnostic.invalid-string]
+r[attributes.diagnostic.on_unimplemented.invalid-string]
 Invalid format strings may generate a warning, but are otherwise allowed, but may not display as intended.
 Format specifiers may generate a warning, but are otherwise ignored.
 

src/attributes/testing.md

@@ -31,7 +31,7 @@ Test functions must be free, monomorphic functions that take no arguments, and t
 > Note: The test mode is enabled by passing the `--test` argument to `rustc`
 > or using `cargo test`.
 
-r[attributes.testing.success]
+r[attributes.testing.test.success]
 The test harness calls the returned value's [`report`] method, and classifies the test as passed or failed depending on whether the resulting [`ExitCode`] represents successful termination.
 In particular:
 * Tests that return `()` pass as long as they terminate and do not panic.
@@ -84,7 +84,7 @@ r[attributes.testing.should_panic.target]
 A function annotated with the `test` attribute that returns `()` can also be
 annotated with the `should_panic` attribute.
 
-r[attributes.testing.should_panic.behaviour]
+r[attributes.testing.should_panic.behavior]
 The *`should_panic` attribute*
 makes the test only pass if it actually panics.