Merge pull request #802 from ErikJson/master

Fix minor documentation issues

docs/cookbook/mockery_on.rst

@@ -11,7 +11,7 @@ when called. If the closure returns ``true``, Mockery will consider that the
 argument has passed the expectation. If the closure returns ``false``, or a
 "falsey" value, the expectation will not pass.
 
-The ``\Mockery::on()`` matcher can be used in various scenarios — validating
+The ``\Mockery::on()`` matcher can be used in various scenarios — validating
 an array argument based on multiple keys and values, complex string matching...
 
 Say, for example, we have the following code. It doesn't do much; publishes a

docs/cookbook/not_calling_the_constructor.rst

@@ -42,7 +42,7 @@ A better approach is to use runtime partial doubles:
         }
     }
 
-    // This will print "Original constructor called."
+    // This will not print anything
     $mock = \Mockery::mock('MyClass')->makePartial();
     $mock->shouldReceive('foo');
 

docs/reference/expectations.rst

@@ -234,7 +234,7 @@ method which accepts one or more closure:
     $mock->shouldReceive('name_of_method')
         ->andReturnUsing(closure, ...);
 
-Closures can queued by passing them as extra parameters as for ``andReturn()``.
+Closures can be queued by passing them as extra parameters as for ``andReturn()``.
 
 .. note::
 

docs/reference/final_methods_classes.rst

@@ -7,9 +7,9 @@ Dealing with Final Classes/Methods
 One of the primary restrictions of mock objects in PHP, is that mocking
 classes or methods marked final is hard. The final keyword prevents methods so
 marked from being replaced in subclasses (subclassing is how mock objects can
-inherit the type of the class or object being mocked.
+inherit the type of the class or object being mocked).
 
-The simplest solution is not to mark classes or methods as final!
+The simplest solution is to not mark classes or methods as final!
 
 However, in a compromise between mocking functionality and type safety,
 Mockery does allow creating "proxy mocks" from classes marked final, or from

docs/reference/pass_by_reference_behaviours.rst

@@ -26,7 +26,7 @@ method) are reflected in the original variable. An example:
 
     echo $baz; // will echo the integer 2
 
-In the example above, the variable $baz is passed by reference to
+In the example above, the variable ``$baz`` is passed by reference to
 ``Foo::bar()`` (notice the ``&`` symbol in front of the parameter?).  Any
 change ``bar()`` makes to the parameter reference is reflected in the original
 variable, ``$baz``.