diff --git a/docs/02-Concepts/03-Functions-&-Events/01-Overview.md b/docs/02-Concepts/03-Functions-&-Events/01-Overview.md
index 811e836e97..b34085a7fc 100644
--- a/docs/02-Concepts/03-Functions-&-Events/01-Overview.md
+++ b/docs/02-Concepts/03-Functions-&-Events/01-Overview.md
@@ -16,7 +16,7 @@ When using Graphcool, there generally are two different ways how you can deploy
 - Use your own FaaS provider (or any other function provisioning mechanism) to deploy a function and invoke it via an **HTTP webhook**.
 - Use the **Graphcool environment** to deploy your function.
 
-Graphcool currently uses AWS Lambda to deploy functions that you define for the Grap hcool environment. It is however planned to support other FaaS providers in the future as well so that you can choose any provider you prefer.
+Graphcool currently uses AWS Lambda to deploy functions that you define for the Graphcool environment. It is however planned to support other FaaS providers in the future as well so that you can choose any provider you prefer.
 
 
 ## Synchronous vs Asynchronous Functions
@@ -25,4 +25,4 @@ On the Graphcool platform, functions are either invoked _synchronously_ or _asyn
 
 _Synchronous_ functions are most commonly used for transforming and validating data, though there might be other use cases, e.g. related to calling out to 3rd party APIs where awaiting a response is required.  
 
-_Asynchronous_ functions are invoked by _events_ that are happening inside the Graphcool system. An event is always _typed_ (meaning the shape of the data is known upfront) and passed as an input argument to the functions that are associated with it.
\ No newline at end of file
+_Asynchronous_ functions are invoked by _events_ that are happening inside the Graphcool system. An event is always _typed_ (meaning the shape of the data is known upfront) and passed as an input argument to the functions that are associated with it.