diff --git a/docs/configuration/jobs.rst b/docs/configuration/jobs.rst
index cadf392..4e63fac 100644
--- a/docs/configuration/jobs.rst
+++ b/docs/configuration/jobs.rst
@@ -279,7 +279,7 @@ Example config: :sampleconf:`/local.yml`.
 Job Type ``snap`` (snapshot & prune only)
 -----------------------------------------
 
-Job type that only takes snapshots and pruning on the local machine.
+Job type that only takes snapshots and performs pruning on the local machine.
 
 .. list-table::
     :widths: 20 80
diff --git a/docs/configuration/prune.rst b/docs/configuration/prune.rst
index 3d5d6e8..a725f91 100644
--- a/docs/configuration/prune.rst
+++ b/docs/configuration/prune.rst
@@ -178,7 +178,7 @@ Workaround using ``snap`` job
 As a workaround (see GitHub :issue:`102` for development progress), a pruning-only :ref:`snap job <job-snap>` can be defined on the source side:
 The snap job is in charge of snapshot creation & destruction, whereas the source job's role is reduced to just serving snapshots.
 However, since, jobs are run independently, it is possible that the snap job will prune snapshots that are queued for replication / destruction by the remote pull job that connects to the source job.
-There is no possible configuration to avoid this problem with the current version of zrepl.
+Symptoms of such race conditions are spurious replication and destroy errors.
 
 Example configuration:
 
@@ -198,7 +198,7 @@ Example configuration:
     snapshotting:
       type: manual
     root_fs: ...
-     
+
   # pull side
   jobs:
   - type: pull