From 85746661caafc0c2f4740e57106f96c599c22ed8 Mon Sep 17 00:00:00 2001 From: Darren Ranalli Date: Fri, 22 Feb 2002 22:03:38 +0000 Subject: [PATCH] grammar, spelling fixups --- panda/src/doc/ppremake-philosophy.txt | 2 +- panda/src/doc/ppremake-process.txt | 6 +++--- panda/src/doc/ppremake-syntax.txt | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/panda/src/doc/ppremake-philosophy.txt b/panda/src/doc/ppremake-philosophy.txt index 68fe334926..2c61b905c4 100644 --- a/panda/src/doc/ppremake-philosophy.txt +++ b/panda/src/doc/ppremake-philosophy.txt @@ -59,7 +59,7 @@ WHAT IS PPREMAKE, EXACTLY? ppremake, including the meaning of all the variables defined within the various Sources.pp files (see below) and all of the generated output, is almost entirely controlled by scripts written in its own - scripting language. Most of these are control scripts are defined + scripting language. Most of these control scripts are defined in the directory $DTOOL/pptempl. diff --git a/panda/src/doc/ppremake-process.txt b/panda/src/doc/ppremake-process.txt index 09845ccf91..70c8b710ae 100644 --- a/panda/src/doc/ppremake-process.txt +++ b/panda/src/doc/ppremake-process.txt @@ -48,7 +48,7 @@ The following steps are executed when ppremake is invoked: needs to include. The use of System.pp to define these filenames, instead of hardcoding them into ppremake, is consistent with the ppremake philosophy of letting as much of its - behavior as possible to be controlled from within the scripting + behavior as possible be controlled from within the scripting language itself. 3. Once Package.pp has been read, traverse the entire source @@ -76,7 +76,7 @@ The following steps are executed when ppremake is invoked: relationships between different directories within the source hierarchy. Each directory may depend on code from zero or more other directories within the same package. (That is, a directory - may include header files define within another directory, and/or + may include header files defined within another directory, and/or require linking with a library built in that directory.) This inter-directory dependency is critical to determine things @@ -138,5 +138,5 @@ The following steps are executed when ppremake is invoked: directory. Since there may be different kinds of source directories, each with very different makefile requirements, the Template files usually have one large #if condition based on the - value of $[DIR_TYPE], which is set within in each Sources.pp (and + value of $[DIR_TYPE], which is set within each Sources.pp (and is set in System.pp to default to "src"). diff --git a/panda/src/doc/ppremake-syntax.txt b/panda/src/doc/ppremake-syntax.txt index 62536d0e56..f085be35fc 100644 --- a/panda/src/doc/ppremake-syntax.txt +++ b/panda/src/doc/ppremake-syntax.txt @@ -15,7 +15,7 @@ variables defined in Global.pp and related files are declared. There are also a number of individually named scopes, one scope for each directory in the source hierarchy that contains a Sources.pp file. Each of these scopes is a child of the global scope, each of these -defines the varibles defined within its Sources.pp file. The name of +defines the variables defined within its Sources.pp file. The name of each scope is the name of the directory, with a trailing slash. For instance, imagine the following simple directory hierarchy: