diff --git a/readme.md b/readme.md
index 142c7d11..e1fb2ab2 100644
--- a/readme.md
+++ b/readme.md
@@ -23,6 +23,8 @@ There are several areas which need additional attention, including but not limit
 
 ## Getting started
 
+If you have never used AWS Lambda or Docker before, check out this [getting started guide](https://fabianfett.de/getting-started-with-swift-aws-lambda-runtime) which helps you with every step from zero to a running Lambda.
+
 First, create a SwiftPM project and pull Swift AWS Lambda Runtime as dependency into your project
 
  ```swift
@@ -100,7 +102,7 @@ Next, create a `main.swift` and implement your Lambda.
 
  Modeling Lambda functions as Closures is both simple and safe. Swift AWS Lambda Runtime will ensure that the user-provided code is offloaded from the network processing thread such that even if the code becomes slow to respond or gets hang, the underlying process can continue to function. This safety comes at a small performance penalty from context switching between threads. In many cases, the simplicity and safety of using the Closure based API is often preferred over the complexity of the performance-oriented API.
 
- ### Using EventLoopLambdaHandler
+### Using EventLoopLambdaHandler
 
  Performance sensitive Lambda functions may choose to use a more complex API which allows user code to run on the same thread as the networking handlers. Swift AWS Lambda Runtime uses [SwiftNIO](https://github.com/apple/swift-nio) as its underlying networking engine which means the APIs are based on [SwiftNIO](https://github.com/apple/swift-nio) concurrency primitives like the `EventLoop` and `EventLoopFuture`. For example: