docs/149315: [PATCH] Spelling fixes for doc/en_US.ISO8859-1/books/

Jimmy Olgeni olgeni at FreeBSD.org
Thu Aug 5 11:50:07 UTC 2010


>Number:         149315
>Category:       docs
>Synopsis:       [PATCH] Spelling fixes for doc/en_US.ISO8859-1/books/
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 05 11:50:06 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Jimmy Olgeni
>Release:        FreeBSD 8.1-RELEASE i386
>Organization:
>Environment:
>Description:
A few spelling fixes for doc/en_US.ISO8859-1/books/.
>How-To-Repeat:
>Fix:
Index: corp-net-guide/book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/corp-net-guide/book.sgml,v
retrieving revision 1.11
diff -u -r1.11 book.sgml
--- corp-net-guide/book.sgml	29 Nov 2004 21:43:34 -0000	1.11
+++ corp-net-guide/book.sgml	5 Aug 2010 11:44:34 -0000
@@ -1069,7 +1069,7 @@
 	  systems will probably find it cheaper to simply upgrade to Windows
 	  NT Workstation or Win2K.</para>
 
-	<para>ACITS LPR and Win95 have a few printing idosyncracies.  Most
+	<para>ACITS LPR and Win95 have a few printing idiosyncrasies.  Most
 	  Win95 programs, such as Microsoft Word, expect print output to be
 	  spooled on the local hard drive and then metered out to a printer
 	  that is plugged into the parallel port.  Network printing, on the
@@ -1846,7 +1846,7 @@
 	  <literal>nec</literal> in both the name of the printer and the name
 	  of the Spool directory.  With the print spooler LPD, the Spool
 	  directories <emphasis>must</emphasis> be different from each other,
-	  or the spooler gets confused and doesen't print.</para>
+	  or the spooler gets confused and doesn't print.</para>
 
 	<para>After the <filename>/etc/printcap</filename> is modified, the
 	  root user must create the <filename>/var/spool/output/NEC</filename>
Index: dev-model/book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/dev-model/book.sgml,v
retrieving revision 1.17
diff -u -r1.17 book.sgml
--- dev-model/book.sgml	3 Jun 2009 22:31:36 -0000	1.17
+++ dev-model/book.sgml	5 Aug 2010 11:44:35 -0000
@@ -2381,7 +2381,7 @@
                     the FreeBSD web site</ulink>. It shows the number of ports
                     available to FreeBSD in the period 1995 to 2005. It looks
                     like the curve has first grown exponentionally, and then
-                    since the middle of 2001 grown linerly.
+                    since the middle of 2001 grown linearly.
                 </para>
 
                 <para>
Index: developers-handbook/l10n/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml,v
retrieving revision 1.13
diff -u -r1.13 chapter.sgml
--- developers-handbook/l10n/chapter.sgml	29 Apr 2009 17:46:49 -0000	1.13
+++ developers-handbook/l10n/chapter.sgml	5 Aug 2010 11:44:35 -0000
@@ -315,7 +315,7 @@
 	  catalogs with the <makevar>NLSSRCDIR</makevar> &man.make.1;
 	  variable.  The default name of the precompiled catalog files
 	  also follow the naming convention mentioned before.  It can be
-	  overriden by setting the <makevar>NLSNAME</makevar> variable.
+	  overridden by setting the <makevar>NLSNAME</makevar> variable.
 	  There are other options to fine tune the processing of the catalog
 	  files but usually it is not needed, thus they are not described
 	  here.  For further information on <filename>bsd.nls.mk</filename>,
Index: developers-handbook/x86/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/developers-handbook/x86/chapter.sgml,v
retrieving revision 1.18
diff -u -r1.18 chapter.sgml
--- developers-handbook/x86/chapter.sgml	17 Feb 2010 18:20:32 -0000	1.18
+++ developers-handbook/x86/chapter.sgml	5 Aug 2010 11:44:36 -0000
@@ -3152,7 +3152,7 @@
 </programlisting>
 
 <warning><para>
-Do not use this program on files stored on a disk formated
+Do not use this program on files stored on a disk formatted
 by <acronym>&ms-dos;</acronym> or &windows;. There seems to be a
 subtle bug in the FreeBSD code when using <function role="syscall">mmap</function>
 on these drives mounted under FreeBSD: If the file is over
Index: fdp-primer/sgml-markup/chapter.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml,v
retrieving revision 1.79
diff -u -r1.79 chapter.sgml
--- fdp-primer/sgml-markup/chapter.sgml	14 Mar 2010 22:26:02 -0000	1.79
+++ fdp-primer/sgml-markup/chapter.sgml	5 Aug 2010 11:44:37 -0000
@@ -1708,7 +1708,7 @@
 	<para>You will frequently want to refer to both applications and
 	  commands when writing documentation.  The distinction between
 	  them is simple: an application is the name for a suite (or possibly
-	  just 1) of programs that fulfil a particular task.  A command is the
+	  just 1) of programs that fulfill a particular task.  A command is the
 	  name of a program that the user can run.</para>
 
 	<para>In addition, you will occasionally need to list one or more of
Index: porters-handbook/book.sgml
===================================================================
RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v
retrieving revision 1.1069
diff -u -r1.1069 book.sgml
--- porters-handbook/book.sgml	4 Aug 2010 17:58:06 -0000	1.1069
+++ porters-handbook/book.sgml	5 Aug 2010 11:44:40 -0000
@@ -962,7 +962,7 @@
 
 	  <para>It is expected that <makevar>PORTEPOCH</makevar> will
 	    not be used for the majority of ports, and that sensible
-	    use of <makevar>PORTVERSION</makevar> can often pre-empt
+	    use of <makevar>PORTVERSION</makevar> can often preempt
 	    it becoming necessary if a future release of the software
 	    should change the version structure. However, care is
 	    needed by FreeBSD porters when a vendor release is made
@@ -1004,7 +1004,7 @@
 
 	  <para><makevar>PKGNAME</makevar> becomes
 	    <literal>gtkmumble-0.10_1</literal></para>
-
+  
 	  <para>A new version is released by the vendor, numbered <literal>0.2</literal>
 	    (it turns out the author actually intended
 	    <literal>0.10</literal> to actually mean
@@ -1162,7 +1162,7 @@
 	    part of the directory name in a family of ports), the
 	    <replaceable>-compiled.specifics</replaceable> part should state
 	    the compiled-in defaults (the hyphen is optional).  Examples are
-	    papersize and font units.</para>
+	    paper size and font units.</para>
 
 	  <para>The <replaceable>-compiled.specifics</replaceable> part
 	    should be set in the <makevar>PKGNAMESUFFIX</makevar>
@@ -1315,7 +1315,7 @@
 	      <entry>psutils</entry>
 	      <entry>-letter</entry>
 	      <entry>1.13</entry>
-	      <entry>Papersize hardcoded at package build time</entry>
+	      <entry>Paper size hardcoded at package build time</entry>
 	    </row>
 
 	    <row>
@@ -3108,7 +3108,7 @@
 	  make sure you also add them to <filename>distinfo</filename>.
 	  Also, the additional files will normally be extracted into
 	  <makevar>WRKDIR</makevar> as well, which for some ports may
-	  lead to undesirable sideeffects and require special handling.</para>
+	  lead to undesirable side effects and require special handling.</para>
       </sect2>
     </sect1>
 
@@ -3885,7 +3885,7 @@
 	      check for
 	      <filename>/var/db/ports/<replaceable>portname</replaceable>/options</filename>.
 	      If that file does not exist, it will use the values of
-	      <makevar>OPTIONS</makevar> to create a dialogbox where the options
+	      <makevar>OPTIONS</makevar> to create a dialog box where the options
 	      can be enabled or disabled.  Then the
 	      <filename>options</filename> file is saved and the selected
 	      variables will be used when building the port.</para>
@@ -5795,7 +5795,7 @@
 	      neglect to look for includes and/or libraries in the X11
 	      directories.  You can tell <command>qmake</command> to
 	      add directories to the include and library searchpaths
-	      via the commandline, for example:</para>
+	      via the command line, for example:</para>
 
 	    <programlisting>${QMAKE} -unix PREFIX=${PREFIX} INCLUDEPATH+=${LOCALBASE}/include \
 	LIBS+=-L${LOCALBASE}/lib sillyapp.pro</programlisting>
@@ -7978,7 +7978,7 @@
 	      <row>
 		<entry><literal>tolua</literal></entry>
 
-		<entry>Library for accesing C/C++ code</entry>
+		<entry>Library for accessing C/C++ code</entry>
 
 		<entry><literal>4.0-5.0</literal></entry>
 	      </row>
@@ -12462,7 +12462,7 @@
 		    <entry>700044</entry>
 		    <entry>June 7, 2007</entry>
 		    <entry>7.0-CURRENT after changing the argument for
-		      vn_open()/VOP_OPEN() from filedescriptor index to the
+		      vn_open()/VOP_OPEN() from file descriptor index to the
 		      struct file *.</entry>
 		  </row>
 
@@ -14075,7 +14075,7 @@
 	    <note>
 	      <para>If a port would conflict with a currently installed
 		port (for example, if they install a file in the same
-		place that perfoms a different function),
+		place that performs a different function),
 		<link linkend="conflicts">use
 		<makevar>CONFLICTS</makevar> instead</link>.
 		<makevar>CONFLICTS</makevar> will set
@@ -14173,7 +14173,7 @@
 	<para>The correct way for a <filename>Makefile</filename> to
 	  signal that the port can not be installed due to some external
 	  factor (for instance, the user has specified an illegal
-	  combination of build options) is to set a nonblank value to
+	  combination of build options) is to set a non-blank value to
 	  <makevar>IGNORE</makevar>.  This value will be formatted and
 	  shown to the user by <command>make install</command>.</para>
 
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-doc mailing list