Fix the README files.

Author: GillesTourreau

README.md

@@ -26,5 +26,5 @@ Design rules used to make your unit tests more strongly strict.
 
 | Rule | Description |
 | - | - |
-| [MQ1000: Verify() or VerifyAll() methods should be called when instantiate a Mock<T> instances](docs/design/MQ1000.md) | When a static member of a generic type is called, the type argument must be specified for the type. When a generic instance member that does not support inference is called, the type argument must be specified for the member. In these two cases, the syntax for specifying the type argument is different and easily confused. |
-| [MQ1001: The Mock<T> instance behavior should be defined to Strict mode](docs/design/MQ1001.md) | A class declares and implements an instance field that is a System.IDisposable type and the class does not implement IDisposable. A class that declares an IDisposable field indirectly owns an unmanaged resource and should implement the IDisposable interface. |
+| [MQ1000: `Verify()` and `VerifyAll()` methods should be called when instantiate a `Mock<T>` instances](docs/design/MQ1000.md) | When instantiating a `Mock<T>` in the *Arrange* phase of an unit test, `Verify()` or `VerifyAll()` method should be called in the *Assert* phase to check the setup methods has been called. |
+| [MQ1001: The `Mock<T>` instance behavior should be defined to Strict mode](docs/design/MQ1001.md) | When instantiating a `Mock<T>` instance, the `MockBehavior` of the `Mock` instance should be defined to `Strict`. |

docs/design/MQ1000.md

@@ -1,4 +1,4 @@
-# MQ1000: `Verify()` and `VerifyAll()` methods should be called when instantiate a Mock<T> instances
+# MQ1000: `Verify()` and `VerifyAll()` methods should be called when instantiate a `Mock<T>` instances
 
 | Property                            | Value                                                                                      |
 |-------------------------------------|--------------------------------------------------------------------------------------------|