Add information about renaming env.example to .env to avoid confusion…

_chapters/add-a-create-note-api.md

@@ -152,7 +152,13 @@ The `iamRoleStatements` section is telling AWS which resources our Lambda functi
 
 ### Test
 
-Now we are ready to test our new API. To be able to test it on our local we are going to mock the input parameters.
+<img class="code-marker" src="/assets/s.png" />To prepare for testing, you first need to rename the `env.example` file to `.env`.
+
+```bash
+$ mv env.example .env
+```
+
+We'll come back to that later, but now we are ready to test our new API. To be able to test it on our local we are going to mock the input parameters.
 
 <img class="code-marker" src="/assets/s.png" />In our project root, create a `mocks/` directory.
 

_chapters/add-a-get-note-api.md

@@ -104,3 +104,15 @@ The response should look similar to this.
 ```
 
 Next, let's create an API to list all the notes a user has.
+
+---
+
+#### Common Issues
+
+- No response
+
+  If you get no response when you invoke your function, check if you are in the base directory and not inside the /libs directory. If so, run this to move up a directory:
+
+``` bash
+$ cd ..
+```