diff --git a/docs/Binding/README.md b/docs/Binding/README.md
index 1028f289..44c3f350 100644
--- a/docs/Binding/README.md
+++ b/docs/Binding/README.md
@@ -127,7 +127,7 @@ Because `{x:Bind}` uses generated code to achieve its benefits, it requires type
 Starting in Windows 10, `{x:Bind}` allow us to bind functions directly in the XAML files. This enables:
 
 - A simpler way to achieve value conversion
-- A way to resolve Bindings that depend on mnore than one parameter.
+- A way to resolve Bindings that depend on more than one parameter.
 
 We can bind functions located in the code behind of the page or control, and even static functions if we use the XMLNamespace:ClassName.MethodName syntax. Let's see examples of how to use the functions in our Bindings:
 
@@ -255,4 +255,4 @@ We have 2 binding mechanisims: `{x:Bind}` and `{Binding}`.
 
 The new Windows 10 markup extension `{x:Bind}`, is an alternative to `{Binding}`. `{x:Bind}` lacks some features of `{Binding}`, but it runs in less time and less memory than `{Binding}` and supports better debugging. With `{x:Bind}` we can also bind functions and events. 
 
-*Value Converters* are great tools to be used in our UI binding expressions. Their function is to apply some format over the original values of the ViewModels and display them in our Views. 
\ No newline at end of file
+*Value Converters* are great tools to be used in our UI binding expressions. Their function is to apply some format over the original values of the ViewModels and display them in our Views.