summaryrefslogtreecommitdiff
path: root/docs/docbook/projdoc/Compiling.xml
diff options
context:
space:
mode:
authorJohn Terpstra <jht@samba.org>2003-06-20 06:49:48 +0000
committerJohn Terpstra <jht@samba.org>2003-06-20 06:49:48 +0000
commitf17817318b9675cde32a0315498e4e27b0c7bab7 (patch)
tree03595a1480d2be9fbcb51180edfd16162ad597d9 /docs/docbook/projdoc/Compiling.xml
parentd7dfff92c1f4239807a7c20c4346f9c9cdfe5ec7 (diff)
downloadsamba-f17817318b9675cde32a0315498e4e27b0c7bab7.tar.gz
samba-f17817318b9675cde32a0315498e4e27b0c7bab7.tar.bz2
samba-f17817318b9675cde32a0315498e4e27b0c7bab7.zip
Applied Vance Lankhaar's spelling fixes.
(This used to be commit 7eea35ba9f02f465403c21f5c33461035ad56176)
Diffstat (limited to 'docs/docbook/projdoc/Compiling.xml')
-rw-r--r--docs/docbook/projdoc/Compiling.xml6
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/docbook/projdoc/Compiling.xml b/docs/docbook/projdoc/Compiling.xml
index fd890a20ec..279be2fdb4 100644
--- a/docs/docbook/projdoc/Compiling.xml
+++ b/docs/docbook/projdoc/Compiling.xml
@@ -139,7 +139,7 @@ on this system just substitute the correct package name
<option>-r</option> and defining a tag name. A list of branch tag names
can be found on the "Development" page of the samba web site. A common
request is to obtain the latest 3.0 release code. This could be done by
- using the following userinput.
+ using the following command:
</para>
<para>
@@ -283,7 +283,7 @@ example of what you would not want to see would be:
<listitem><para>the MIT kerberos development libraries
(either install from the sources or use a package). The
- heimdal libraries will not work.</para></listitem>
+ Heimdal libraries will not work.</para></listitem>
<listitem><para>the OpenLDAP development libraries.</para></listitem>
@@ -345,7 +345,7 @@ example of what you would not want to see would be:
<title>Starting the &smbd; and &nmbd;</title>
<para>You must choose to start &smbd; and &nmbd; either
- as daemons or from <application>inetd</application>Don't try
+ as daemons or from <application>inetd</application>. Don't try
to do both! Either you can put them in <filename>
inetd.conf</filename> and have them started on demand
by <application>inetd</application>, or you can start them as