Apply some light edits to the conventions chapter

Author: ehuss

src/conventions.md

@@ -7,7 +7,7 @@ Like all technical books, this book has certain conventions in how it displays i
 ## Rules
 
 r[example.rule.label]
-Rule identifiers appear before each language rule enclosed in square brackets. These identifiers provide a way to refer to and link to a specific rule in the language ([e.g.][example rule]). The rule identifier uses periods to separate sections from most general to most specific ([destructors.scope.nesting.function-body] for example). On narrow screens, the rule name will collapse to display `[*]`.
+Rule identifiers appear before each language rule, enclosed in square brackets. These identifiers provide a way to refer to and link to a specific rule in the language ([e.g.][example rule]). The rule identifier uses periods to separate sections from most general to most specific ([destructors.scope.nesting.function-body] for example). On narrow screens, the rule name will collapse to display `[*]`.
 
 The rule name can be clicked to link to that rule.
 
@@ -16,16 +16,18 @@ The rule name can be clicked to link to that rule.
 
 ### Rule tests
 
-Rules that have associated tests will include a `Tests` link below them (on narrow screens, the link is `[T]`). Clicking the link will pop up a list of tests, which can be clicked to view the test. For example, see [input.encoding.utf8].
+Rules that have associated tests will include a `Tests` link below them (on narrow screens, the link is `[T]`). Clicking the link will display a list of tests, which can be clicked to view each test. For example, see [input.encoding.utf8].
 
-Linking rules to tests is an ongoing effort. See the [Test summary](test-summary.md) chapter for an overview.
+Linking rules to tests is an ongoing effort. See the [test summary] chapter for an overview.
 
 ## Definitions
 
 Statements that define a term contain that term in *italics*. Whenever that term is used outside of that chapter, it is usually a link to the section that has this definition.
 
 An *example term* is an example of a term being defined.
 
+The [glossary] contains a list of definitions.
+
 ## Examples
 
 Example blocks show an example that demonstrates some rule or points out some interesting aspect. Some examples may have hidden lines which can be viewed by clicking the eye icon that appears when hovering or tapping the example.
@@ -38,22 +40,20 @@ Example blocks show an example that demonstrates some rule or points out some in
 
 ## Code blocks
 
-Code snippets inline in the text are inside `<code>` tags.
-
-Longer code examples are in a syntax highlighted box that has controls for copying, executing, and showing hidden lines in the top right corner.
+Code examples have controls for copying, executing, and showing hidden lines in the top right corner.
 
 ```rust
 # // This is a hidden line.
 fn main() {
-  println!("This is a code example");
+    println!("This is a code example");
 }
 ```
 
 All examples are written for the latest edition unless otherwise stated.
 
 ## Grammar
 
-The grammar and lexical productions are described in the [Notation] chapter.
+The grammar and lexical productions are described in the [grammar notation chapter][notation].
 
 ## Notes
 
@@ -77,3 +77,5 @@ The main text describes the latest stable edition. Differences to previous editi
 > Before the 2018 edition, the behavior was this. As of the 2018 edition, the behavior is that.
 
 [example rule]: example.rule.label
+[Glossary]: glossary.md
+[test summary]: test-summary.md