* user-guide.texinfo, install.texinfo: Cleanup makeinfo warning of

	not having `.' or `,' after @xref.

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@13513 dc483132-0cff-0310-8789-dd5450dbe970

diff --git a/doc/ChangeLog b/doc/ChangeLog
index e302e05b8127d3fd4595840713d70811fcf763ba..d85ad0849782c7d7132733895fe4defa9cb0075e 100644 (file)
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,8 @@
+2001-06-26  Ezra Peisach  <epeisach@mit.edu>
+
+       * user-guide.texinfo, install.texinfo: Cleanup makeinfo warning of
+       not having `.' or `,' after @xref.
+
 2001-01-19  Ken Raeburn  <raeburn@mit.edu>
 
        * coding-style: Assume ANSI C '89.  Use krb5int_ for internal

diff --git a/doc/install.texinfo b/doc/install.texinfo
index e1f6fa5608e44dda0d225d16afe3538875de9c59..85dbbb705870251680170694cdb4688a5aa15a90 100644 (file)
--- a/doc/install.texinfo
+++ b/doc/install.texinfo
@@ -1166,7 +1166,7 @@ counterparts
 @subsection Client Machine Configuration Files
 
 Each machine running Kerberos must have a @code{/etc/krb5.conf} file.
-(@xref{krb5.conf})
+(@xref{krb5.conf}.)
 
 @need 4000
 Also, for most UNIX systems, you must add the appropriate Kerberos
@@ -1400,7 +1400,7 @@ In order to generate a keytab for a host, the host must have a principal
 in the Kerberos database.  The procedure for adding hosts to the
 database is described fully in the ``Adding or Modifying Principals''
 section of the @cite{@value{PRODUCT} System Administrator's Guide}.
-@xref{Create Host Keys for the Slave KDCs} for a brief description.)
+@xref{Create Host Keys for the Slave KDCs}. for a brief description.)
 The keytab is generated by running @code{kadmin} and issuing the
 @code{ktadd} command.
 
@@ -1492,7 +1492,7 @@ server processes, if any.
 @end smallexample
 
 @item Create a new Master KDC installation (@xref{Install the Master
-KDC}).  If you have a stash file for your current database, choose any
+KDC}.).  If you have a stash file for your current database, choose any
 new master password but then copy your existing stash file to the
 location specified by your kdc.conf; if you do not have a stash file for
 your current database, you must choose the same master password.

diff --git a/doc/user-guide.texinfo b/doc/user-guide.texinfo
index c60be114b80b8718182706f31ad41861c00f789b..59b9b08c53551d9bfedde3d0b4a80795af62678e 100644 (file)
--- a/doc/user-guide.texinfo
+++ b/doc/user-guide.texinfo
@@ -444,7 +444,7 @@ post@b{d}ated
 Here is a sample listing.  In this example, the user @value{RANDOMUSER1}
 obtained her initial tickets (@samp{I}), which are forwardable
 (@samp{F}) and postdated (@samp{d}) but not yet validated (@samp{i}).
-(@xref{kinit Reference} for more information about postdated tickets.)
+(@xref{kinit Reference}, for more information about postdated tickets.)
 
 @smallexample
 @group
@@ -663,7 +663,7 @@ If you need to give someone access to log into your account, you can do
 so through Kerberos, without telling the person your password.  Simply
 create a file called @code{.k5login} in your home directory.  This file
 should contain the Kerberos principal (@xref{What is a Kerberos
-Principal?}) of each person to whom you wish to give access.  Each
+Principal?}.) of each person to whom you wish to give access.  Each
 principal must be on a separate line.  Here is a sample @code{.k5login}
 file: