diff --git a/doc/event-notifications.xml b/doc/event-notifications.xml
index 47c3837f..f43c7f00 100644
--- a/doc/event-notifications.xml
+++ b/doc/event-notifications.xml
@@ -148,7 +148,7 @@
   the notification types can be filtered to explicitly named ones using the
   <varname>event_notifications</varname> parameter, e.g.:
     <programlisting>
-    event_notifications=primary_register,standby_register,witness_register</programlisting>
+    event_notifications='primary_register,standby_register,witness_register;</programlisting>
 
  </para>
 
diff --git a/doc/repmgrd-bdr.xml b/doc/repmgrd-bdr.xml
index bae11e98..90b813fd 100644
--- a/doc/repmgrd-bdr.xml
+++ b/doc/repmgrd-bdr.xml
@@ -94,7 +94,7 @@
         replication_type='bdr'
 
         # Event notification configuration
-        event_notifications=bdr_failover
+        event_notifications='bdr_failover'
         event_notification_command='/path/to/bdr-pgbouncer.sh %n %e %s "%c" "%a" >> /tmp/bdr-failover.log 2>&amp;1'
 
         # repmgrd options
diff --git a/doc/repmgrd-node-fencing.md b/doc/repmgrd-node-fencing.md
index 58c0eafd..f09c9a12 100644
--- a/doc/repmgrd-node-fencing.md
+++ b/doc/repmgrd-node-fencing.md
@@ -146,7 +146,7 @@ Script and template file should be installed on each node where `repmgrd` is run
 Finally, set `promote_command` in `repmgr.conf` on each node to
 point to the custom promote script:
 
-    promote_command=/var/lib/postgres/repmgr/promote.sh
+    promote_command='/var/lib/postgres/repmgr/promote.sh'
 
 and reload/restart any running `repmgrd` instances for the changes to take
 effect.