Fix typos and make minor structural changes

Author: James Calcaben

guides/v2.0/extension-dev-guide/plugins.md

@@ -134,7 +134,9 @@ class ProductPlugin
 ?>
 {% endhighlight %}
 
-When you wrap a method which accepts arguments, your plugin must also accept those arguments and you must forward them on when you invoke the <code>proceed</code> callable. You must be careful to match the original signature of the method with regards to default parameters and type hints. For example, the following code defines a parameter of type <code>SomeType>/code> which is nullable:
+When you wrap a method which accepts arguments, your plugin must also accept those arguments and you must forward them when you invoke the <code>proceed</code> callable. You must be careful to match the original signature of the method with regards to default parameters and type hints. 
+
+For example, the following code defines a parameter of type <code>SomeType</code> which is nullable:
 
 {% highlight PHP %}
 <?php
@@ -168,7 +170,7 @@ class MyUtilityPlugin
 
 Note the missing <code>= null</code>. Now, if the original method was called with <code>null</code> PHP would throw a fatal error as your plugin does not accept <code>null</code>.
 
-It is also worth noting that you are responsible for forwarding the arguments from the plugin to the <code>proceed</code> callable. If you are not using/modifying the agurments, you could use variadics and argument unpacking to achieve this simply:
+It is also worth noting that you are responsible for forwarding the arguments from the plugin to the <code>proceed</code> callable. If you are not using/modifying the arguments, you could use variadics and argument unpacking to achieve this simply:
 
 {% highlight PHP %}
 <?php