Fix POD errors in fileserver and dasalvager

Fix missing newlines before =back commands.

Change-Id: If8e65c94f48c271c37c1b4bbec1b17d383c8375d
Reviewed-on: http://gerrit.openafs.org/2831
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Derrick Brashear <shadow@dementia.org>
Tested-by: Derrick Brashear <shadow@dementia.org>

diff --git a/doc/man-pages/pod8/fileserver.pod.in b/doc/man-pages/pod8/fileserver.pod.in
index 3002f80..31999b0 100644 (file)
--- a/doc/man-pages/pod8/fileserver.pod.in
+++ b/doc/man-pages/pod8/fileserver.pod.in
@@ -33,6 +33,7 @@ file server machine as the local superuser C<root>.
 =head1 OPTIONS
 
 =include fragments/fileserver-options.pod
+
 =back
 
 =head1 EXAMPLES

diff --git a/doc/man-pages/pod8/fragments/salvager-description.pod b/doc/man-pages/pod8/fragments/salvager-description.pod
index 43996ca..9cfb962 100644 (file)
--- a/doc/man-pages/pod8/fragments/salvager-description.pod
+++ b/doc/man-pages/pod8/fragments/salvager-description.pod
@@ -19,6 +19,7 @@ corruption as it initializes, it sometimes refuses to attach the volume or
 bring it online. In this case, it is simplest to remove the volume by
 issuing the B<vos remove> or B<vos zap> command. Then issue the B<vos
 release> or B<vos backup> command to create it again.
+
 =back
 
 Unlike other server process initialization commands, the Salvager