diff --git a/payload/spacedb/README.md b/payload/spacedb/README.md
index 461ceff..ac9bb4d 100644
--- a/payload/spacedb/README.md
+++ b/payload/spacedb/README.md
@@ -256,7 +256,7 @@ critical-tel-check  info: Scheduler service comms started successfully at: 3.19.
 We visit the provided URL and find another graphiql interface. According to the [KubOS documentation](https://docs.kubos.com/1.19.0/ecosystem/services/scheduler.html), we may issue the following query to enter safe mode and stop any subsequent checks which might kill the scheduler and bring us back to where we started:
 ```
 mutation safe {
-`	safeMode{success, errors}
+	safeMode{success, errors}
 }
 ```
 We also see that we can dump the task lists for all available modes with the following query:
@@ -269,8 +269,7 @@ query dump {
 From the information from the dumped task lists, we can see that there are several tasks we may run. First and foremost, we need to fix our power situation by orienting the solar panels towards the sun. We may do this by running the following mutation:
 ```
 mutation patch {
-
-createMode(name: "patch"){success, errors}
+	createMode(name: "patch"){success, errors}
 	importRawTaskList(name: "patch", mode: "patch", json: "{\"tasks\":[{\"description\":\"Orient solar panels at sun.\",\"delay\":\"0s\",\"time\":null,\"period\":null,\"app\":{\"name\":\"sunpoint\",\"args\":null,\"config\":null}},{\"description\":\"Update system telemetry\",\"delay\":\"1s\",\"time\":null,\"period\":null,\"app\":{\"name\":\"update_tel\",\"args\":null,\"config\":null}}]}"){success, errors}
 	activateMode(name: "patch"){success, errors}
 }