diff --git a/README.md b/README.md
index f53f56544..75051c335 100644
--- a/README.md
+++ b/README.md
@@ -38,12 +38,9 @@ There is a browser-friendly version of this documentation at
 
 ## Google Summer of Code
 
-The Postgres Operator made it to the [Google Summer of Code 2019](https://summerofcode.withgoogle.com/)!
-As a brand new mentoring organization, we are now looking for our first mentees.
+The Postgres Operator made it to the [Google Summer of Code 2019](https://summerofcode.withgoogle.com/organizations/5429926902104064/)!
 Check [our ideas](docs/gsoc-2019/ideas.md#google-summer-of-code-2019)
-and start discussion in [the issue tracker](https://github.com/zalando/postgres-operator/issues).
-And don't forget to spread a word about our GSoC participation to attract even
-more students.
+and start discussions in [the issue tracker](https://github.com/zalando/postgres-operator/issues).
 
 ## Community
 
diff --git a/docs/quickstart.md b/docs/quickstart.md
index ca341e6fe..571a94493 100644
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -166,8 +166,10 @@ kubectl delete postgresql acid-minimal-cluster
 
 This should remove the associated StatefulSet, database Pods, Services and
 Endpoints. The PersistentVolumes are released and the PodDisruptionBudget is
-deleted. Secrets however are not deleted. When deleting a cluster while it is
-still starting up it can [happen](https://github.com/zalando/postgres-operator/issues/551)
-the `postgresql` resource is deleted leaving orphaned components behind. This
-can cause troubles when creating a new Postgres cluster. For a fresh setup you
-can delete your local minikube or kind cluster and start again.
+deleted. Secrets however are not deleted and backups will remain in place.
+
+When deleting a cluster while it is still starting up or got stuck during that
+phase it can [happen](https://github.com/zalando/postgres-operator/issues/551)
+that the `postgresql` resource is deleted leaving orphaned components behind.
+This can cause troubles when creating a new Postgres cluster. For a fresh setup
+you can delete your local minikube or kind cluster and start again.
diff --git a/docs/reference/cluster_manifest.md b/docs/reference/cluster_manifest.md
index 98119df2c..44500bc66 100644
--- a/docs/reference/cluster_manifest.md
+++ b/docs/reference/cluster_manifest.md
@@ -153,8 +153,7 @@ required in the manifest.
 * **parameters**
   a dictionary of Postgres parameter names and values to apply to the resulting
   cluster. Optional (Spilo automatically sets reasonable defaults for parameters
-  like work_mem or max_connections).
-
+  like `work_mem` or `max_connections`).
 
 ## Patroni parameters
 
@@ -198,7 +197,7 @@ explanation of `ttl` and `loop_wait` parameters.
 * **slots**
   permanent replication slots that Patroni preserves after failover by
   re-creating them on the new primary immediately after doing a promote. Slots
-  could be reconfigured with the help of `Patronictl edit-config`. It is the
+  could be reconfigured with the help of `patronictl edit-config`. It is the
   responsibility of a user to avoid clashes in names between replication slots
   automatically created by Patroni for cluster members and permanent replication
   slots. Optional.