Just a few nits (#188)

Author: bkoelman

_includes/0001_Introduction.md

@@ -1,6 +1,6 @@
 ## 1.1. What is this?
 
-This document attempts to provide guidelines (or coding standards if you like) for all versions of C# up to and including that are both valuable and pragmatic. Of course, if you create such a document you should practice what you preach. So rest assured, these guidelines are representative to what we at [Aviva Solutions](https://www.avivasolutions.nl) do in our day-to-day work. Notice that not all guidelines have a clear rationale. Some of them are simply choices we made at Aviva Solutions. In the end, it doesn't matter what choice you made, as long as you make one and apply it consistently.
+This document attempts to provide guidelines (or coding standards if you like) for all versions of C# up to and including 7.3 that are both valuable and pragmatic. Of course, if you create such a document you should practice what you preach. So rest assured, these guidelines are representative to what we at [Aviva Solutions](https://www.avivasolutions.nl) do in our day-to-day work. Notice that not all guidelines have a clear rationale. Some of them are simply choices we made at Aviva Solutions. In the end, it doesn't matter what choice you made, as long as you make one and apply it consistently.
 
 ## 1.2. Why would you use this document?
 

_pages/1100_MemberDesignGuidelines.md

@@ -46,7 +46,7 @@ You generally don't want callers to be able to change an internal collection, so
 
 ### <a name="av1135"></a> Properties, arguments and return values representing strings or collections should never be `null` (AV1135) ![](/assets/images/1.png)
 
-Returning `null` can be unexpected by the caller. Always return an empty collection or an empty string instead of a `null` reference. When your member return `Task` or `Task<T>`, return `Task.CompletedTask` or `Task.FromResult()`. This also prevents cluttering your code base with additional checks for `null`, or even worse, `string.IsNullOrEmpty()`.
+Returning `null` can be unexpected by the caller. Always return an empty collection or an empty string instead of a `null` reference. When your member returns `Task` or `Task<T>`, return `Task.CompletedTask` or `Task.FromResult()`. This also prevents cluttering your code base with additional checks for `null`, or even worse, `string.IsNullOrEmpty()`.
 
 ### <a name="av1137"></a> Define parameters as specific as possible (AV1137) ![](/assets/images/2.png)
 

_pages/Cheatsheet.md

@@ -136,7 +136,7 @@ NOTE: Requires Markdown Extra. See http://michelf.ca/projects/php-markdown/extra
 <td class="column" markdown="1">
 <div class="sidebar">
 
-| **Pascal Casing**                     |                                                             |
+| **Symbol kind**                       | **Example**                                                 |
 |:--------------------------------------|-------------------------------------------------------------|
 | Namespace                             | `System.Drawing`                                            |
 | Type parameter                        | `TView`                                                     |