diff --git a/docs/ipsets.xml b/docs/ipsets.xml
index 3dc14bb0e..f2d1bff61 100644
--- a/docs/ipsets.xml
+++ b/docs/ipsets.xml
@@ -179,22 +179,25 @@ ACCEPT net:+sshok $FW tcp 22
Beginning with Shorewall 4.6.4, SAVE_IPSETS is available in shorewall6-conf(5). When set
- to Yes, the ipv6 ipsets will be set. You can also save selective ipsets by
- setting SAVE_IPSETS to a comma-separated list of ipset names.
+ to Yes, the ipv6 ipsets will be saved. You can also save selective ipsets
+ by setting SAVE_IPSETS to a comma-separated list of ipset names.
- Prior to Shorewall 4.6.4, SAVE_IPSETS=Yes in shorewall.conf won't
- work correctly because it saves both IPv4 and IPv6 ipsets. To work around
- this issue, Shorewall-init is capable restoring ipset contents during
- 'start' and saving them during 'stop'. To direct Shorewall-init to
- save/restore ipset contents, set the SAVE_IPSETS option in
+ Prior to Shorewall 4.6.4, SAVE_IPSETS=Yes in shorewall.conf(5) won't work
+ correctly because it saves both IPv4 and IPv6 ipsets. To work around this
+ issue, Shorewall-init is capable restoring ipset contents during 'start'
+ and saving them during 'stop'. To direct Shorewall-init to save/restore
+ ipset contents, set the SAVE_IPSETS option in
/etc/sysconfig/shorewall-init (/etc/default/shorewall-init on Debian and
derivatives). The value of the option is a file name where the contents of
the ipsets will be save to and restored from. Shorewall-init will create
- any necessary directories during the first 'save' operation. If you
- configure Shorewall-init to save/restore ipsets, be sure to set
- SAVE_IPSETS=No in shorewall.conf and shorewall6.conf. If you configure
- SAVE_IPSETS in both shorewall.conf(5) and
+
+ If you configure Shorewall-init to save/restore ipsets, be sure to
+ set SAVE_IPSETS=No in shorewall.conf and shorewall6.conf.
+
+ If you configure SAVE_IPSETS in shorewall.conf(5) and/or shorewall6.conf(5) then do
not set SAVE_IPSETS in shorewall-init.