Merge pull request #322 from mrgeorg/patch-1

Variable.rst: correct typos

docs/source/tutorial/variables.rst

@@ -60,7 +60,7 @@ You can interact with the variables like this:
 		return 0;
 	}
 
-From this example, you can see that there's many ways to pull out the varaibles you want. You can get  For example, to determine if a nested variable exists or not, you can use ``auto`` to capture the value of a ``table[key]`` lookup, and then use the ``.valid()`` method:
+From this example, you can see that there's many ways to pull out the varaibles you want. For example, to determine if a nested variable exists or not, you can use ``auto`` to capture the value of a ``table[key]`` lookup, and then use the ``.valid()`` method:
 
 .. code-block:: cpp
 	:caption: safe lookup
@@ -83,7 +83,7 @@ This comes in handy when you want to check if a nested variable exists. You can
 		// Branch not taken: value is not an integer
 	}
 
-	sol::optoinal<bool> is_a_boolean = lua["config"]["fullscreen"];
+	sol::optional<bool> is_a_boolean = lua["config"]["fullscreen"];
 	if (is_a_boolean) {
 		// Branch taken: the value is a boolean
 	}
@@ -199,4 +199,4 @@ Finally, it's possible to erase a reference/variable by setting it to ``nil``, u
 		// y will not have a value
 	}
 
-It's easy to see that there's a lot of options to do what you want here. But, these are just traditional numbers and strings. What if we want more power, more capabilities than what these limited types can offer us? Let's throw some :doc:`functions in there<functions>` :doc:`C++ classes into the mix<cxx-in-lua>`!
+It's easy to see that there's a lot of options to do what you want here. But, these are just traditional numbers and strings. What if we want more power, more capabilities than what these limited types can offer us? Let's throw some :doc:`functions in there<functions>` :doc:`C++ classes into the mix<cxx-in-lua>`!