Index: openacs-4/packages/acs-core-docs/www/install-next-backups.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-next-backups.adp,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/acs-core-docs/www/install-next-backups.adp	7 Aug 2017 23:47:50 -0000	1.2
+++ openacs-4/packages/acs-core-docs/www/install-next-backups.adp	8 Nov 2017 09:42:11 -0000	1.3
@@ -23,10 +23,10 @@
 that you are more likely to do it.</p></li>
 </ul></div><p>OpenACS installations comprise files and database contents. If
 you follow the reference install and put all files, including
-configuration files, in <code class="filename">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/</code>,
-and back up the database nightly to a file in <code class="filename">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/database-backup</code>,
+configuration files, in <code class="filename">/var/lib/aolserver/<em class="replaceable"><code>$OPENACS_SERVICE_NAME</code></em>/</code>, and
+back up the database nightly to a file in <code class="filename">/var/lib/aolserver/<em class="replaceable"><code>$OPENACS_SERVICE_NAME</code></em>/database-backup</code>,
 then you can apply standard file-based backup strategies to
-<code class="filename">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
+<code class="filename">/var/lib/aolserver/<em class="replaceable"><code>$OPENACS_SERVICE_NAME</code></em>
 </code>
 </p>
 </div>