Merge pull request #667 from fabioberger/patch-1

Documentation Typos

2 files changed, 2 insertions, 2 deletions

diff --git a/docs/miscellaneous.rst b/docs/miscellaneous.rst
index c9a8890f..c883815c 100644
--- a/docs/miscellaneous.rst
+++ b/docs/miscellaneous.rst
@@ -161,7 +161,7 @@ Unfortunately, there are some subtleties the compiler does not yet warn you abou
   2. Sending Ether can fail due to the call depth going above 1024. Since the caller is in total control of the call
      depth, they can force the transfer to fail, so make sure to always check the return value of ``send``. Better yet,
      write your contract using a pattern where the recipient can withdraw Ether instead.
-  3. Sending Ether can also fail because the recipient goes out of gas (either explicitly by using ``throw`` or
+  3. Sending Ether can also fail because the recipient runs out of gas (either explicitly by using ``throw`` or
      because the operation is just too expensive). If the return value of ``send`` is checked, this might provide a
      means for the recipient to block progress in the sending contract. Again, the best practise here is to use
      a "withdraw" pattern instead of a "send" pattern.
diff --git a/docs/types.rst b/docs/types.rst
index 9de83843..515c200f 100644
--- a/docs/types.rst
+++ b/docs/types.rst
@@ -10,7 +10,7 @@ Solidity is a statically typed language, which means that the type of each
 variable (state and local) needs to be specified (or at least known -
 see :ref:`type-deduction` below) at
 compile-time. Solidity provides several elementary types which can be combined
-to complex types.
+to form complex types.
 
 .. index:: ! value type, ! type;value