Browse Source

typo, whitespace, and a clarification

svn:r6605
Roger Dingledine 19 years ago
parent
commit
d90d4b4c90
2 changed files with 13 additions and 12 deletions
  1. 5 4
      doc/tor-osx-dmg-creation.txt
  2. 8 8
      doc/tor-rpm-creation.txt

+ 5 - 4
doc/tor-osx-dmg-creation.txt

@@ -2,7 +2,8 @@ The following steps are the exact steps used to produce the "official"
 OSX builds of tor
 OSX builds of tor
 
 
 Summary:
 Summary:
-1) Compile and install the latest release of libevent
+1) Compile and install a static version of the latest release of
+libevent.
 2) Acquire privoxyosx_setup_3.0.3.zip.  Remember where you put this
 2) Acquire privoxyosx_setup_3.0.3.zip.  Remember where you put this
 file.
 file.
 3) Acquire and install your preferred version of tor via "make
 3) Acquire and install your preferred version of tor via "make
@@ -11,7 +12,7 @@ dist-osx"
 Details:
 Details:
 ### Compiling libevent
 ### Compiling libevent
 
 
-1)  Download the latest libevent from 
+1)  Download the latest libevent from
 http://www.monkey.org/~provos/libevent/
 http://www.monkey.org/~provos/libevent/
 
 
 2) The first step of compiling libevent is to configure it as
 2) The first step of compiling libevent is to configure it as
@@ -27,8 +28,8 @@ or sudo -s, to complete the "make install".
 1) Download osx privoxy source from
 1) Download osx privoxy source from
 http://prdownloads.sourceforge.net/ijbswa/privoxyosx_setup_3.0.3.zip?download
 http://prdownloads.sourceforge.net/ijbswa/privoxyosx_setup_3.0.3.zip?download
 
 
-2) Edit /path/to/tor/contrib/osx/package.sh and confirm 
+2) Edit /path/to/tor/contrib/osx/package.sh and confirm
-PRIVOXY_PKG_ZIP= is set to the correct path to find the 
+PRIVOXY_PKG_ZIP= is set to the correct path to find the
 file privoxyosx_setup_3.0.3.zip
 file privoxyosx_setup_3.0.3.zip
 
 
 
 

+ 8 - 8
doc/tor-rpm-creation.txt

@@ -1,13 +1,13 @@
-These are instructions for building Tor binaries in the rpm format on 
+These are instructions for building Tor binaries in the rpm format on
 various cpu architectures and operating systems.  Each rpm will require
 various cpu architectures and operating systems.  Each rpm will require
-glibc on the target system.  It is believed that any rpm-based linux 
+glibc on the target system.  It is believed that any rpm-based linux
-distribution should have semi-current glibc installed by default.  
+distribution should have semi-current glibc installed by default.
-If you run into a distribution that does not work with glibc, or does 
+If you run into a distribution that does not work with glibc, or does
-not contain it, please let us know the details.  
+not contain it, please let us know the details.
 
 
 These are the exact same steps used to build the official rpms of Tor.
 These are the exact same steps used to build the official rpms of Tor.
 
 
-If you wish to further tune Tor binaries in rpm format beyond this list, 
+If you wish to further tune Tor binaries in rpm format beyond this list,
 see the GCC doc page for further options:
 see the GCC doc page for further options:
 http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/
 http://gcc.gnu.org/onlinedocs/gcc-4.0.2/gcc/
 
 
@@ -26,11 +26,11 @@ this:
 
 
 The three parameters: target, target_cpu, and target_os are used
 The three parameters: target, target_cpu, and target_os are used
 throughout the "make dist-rpm" process.  They control the parameters
 throughout the "make dist-rpm" process.  They control the parameters
-passed to "configure" and the final tuning of the binaries produced.  
+passed to "configure" and the final tuning of the binaries produced.
 The default settings, as shown above, create binaries for the widest
 The default settings, as shown above, create binaries for the widest
 range of Intel x86 or compatible architectures.
 range of Intel x86 or compatible architectures.
 
 
-The paramters can be set as follows:
+The parameters can be set as follows:
 
 
 The "target" parameter:
 The "target" parameter:
 This should be "gnu", "redhat", or the short name of your linux distribution.
 This should be "gnu", "redhat", or the short name of your linux distribution.