summaryrefslogtreecommitdiff
path: root/doc/guide
diff options
context:
space:
mode:
authorwiz <wiz@pkgsrc.org>2005-05-10 22:41:10 +0000
committerwiz <wiz@pkgsrc.org>2005-05-10 22:41:10 +0000
commit5683ea907d2c2ed95b6fccfc463925d374a366b3 (patch)
tree7b0e626d1c8162708016fe7a6572894599062db8 /doc/guide
parentd0a8978cf59a31c73845d74a9ddbc5fa5d9aadcd (diff)
downloadpkgsrc-5683ea907d2c2ed95b6fccfc463925d374a366b3.tar.gz
Some fixes and minor improvements.
Diffstat (limited to 'doc/guide')
-rw-r--r--doc/guide/files/makefile.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/guide/files/makefile.xml b/doc/guide/files/makefile.xml
index 80aacad64f9..1aa60135d17 100644
--- a/doc/guide/files/makefile.xml
+++ b/doc/guide/files/makefile.xml
@@ -1,4 +1,4 @@
-<!-- $NetBSD: makefile.xml,v 1.2 2005/05/10 01:15:54 rillig Exp $ -->
+<!-- $NetBSD: makefile.xml,v 1.3 2005/05/10 22:41:10 wiz Exp $ -->
<chapter id="makefile"> <?dbhtml filename="makefile.html"?>
<title>Programming in <filename>Makefile</filename>s</title>
@@ -29,7 +29,7 @@
<para>A restriction common to all types of variables is that they
can neither contain a newline character nor the '\0' character nor
- the '#' character. The effects of the backslash character is not
+ the '#' character. The effects of the backslash character are not
documented, so you should not use it at the moment. As the $ is used
to get values of a <filename>Makefile</filename> variable, it must
be quoted as $$.</para>
@@ -57,7 +57,7 @@
may be exported to a shell command. Their elements can contain any
characters, including whitespace. That's why they cannot be used
in <!-- FIXME --><varname>.for</varname> loops. Examples are
- <varname>DISTFILES</varname>,
+ <varname>DISTFILES</varname> and
<varname>MASTER_SITES</varname>.</para></listitem>
</itemizedlist>
@@ -130,12 +130,12 @@ all:
<para>Example 1 leads to a syntax error in the shell, as the
characters are just copied.</para>
- <para>Example 2 leads to a syntax error too, and when you leave
- out the last " character from <varname>${ATOM}</varname> the
+ <para>Example 2 leads to a syntax error too, and if you leave
+ out the last " character from <varname>${ATOM}</varname>,
&man.date.1; would be executed. The <varname>$HOME</varname> shell
variable would be evaluated, too.</para>
- <para>Example 3 would output precede each space character with a
+ <para>Example 3 would output each space character preceded by a
backslash (or not), depending on the implementation of the
&man.echo.1; command.</para>