s/in to/into/ where it makes sense.

This commit can very likely be ignored by translators.
This commit is contained in:
Ceri Davies 2002-05-22 08:36:43 +00:00
parent 1afb1300c1
commit 1f37332cae
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=13193
8 changed files with 26 additions and 26 deletions
en_US.ISO8859-1/books
developers-handbook/policies
faq
fdp-primer
sgml-markup
sgml-primer
structure
the-website
translations
porters-handbook

View file

@ -288,7 +288,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<listitem>
<para>The <firstterm>Release Engineer</firstterm>
decides whether or not it goes in to the release.</para>
decides whether or not it goes into the release.</para>
</listitem>
</orderedlist>
</listitem>
@ -306,7 +306,7 @@ obrien@FreeBSD.org - 30 March 1997</programlisting>
<listitem>
<indexterm><primary>release engineer</primary></indexterm>
<para>The <ulink url="../../articles/contributors/staff-who.html">Release Engineer</ulink>
decides if it goes in to the release.</para>
decides if it goes into the release.</para>
</listitem>
</orderedlist>
</listitem>

View file

@ -764,7 +764,7 @@
<entry>Microsoft's Rich Text Format<footnote>
<para>Page numbers are not automatically updated
when loading this format in to Word. Press
when loading this format into Word. Press
<keycombo action="simul"><keycap>CTRL</keycap><keycap>A</keycap></keycombo>,
<keycombo action="simul"><keycap>CTRL</keycap><keycap>END</keycap></keycombo>,
<keycap>F9</keycap> after loading the document, to
@ -898,13 +898,13 @@ File: +COMMENT (ignored)
File: +DESC (ignored)</screen>
<para>As you can see, <filename>book.pdf</filename> will have been
installed in to
installed into
<filename>/usr/share/doc/en_US.ISO8859-1/books/faq</filename>.
</para>
<para>If you do not want to use the packages then you will have to
download the compressed files yourself, uncompress them, and then
copy the appropriate documents in to place.</para>
copy the appropriate documents into place.</para>
<para>For example, the split HTML version of the FAQ, compressed
using &man.gzip.1;, can be found in the
@ -3151,7 +3151,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
</question>
<answer>
<para>Go in to the BIOS setup and disable the <quote>boot virus
<para>Go into the BIOS setup and disable the <quote>boot virus
protection</quote>.</para>
</answer>
</qandaentry>
@ -3471,7 +3471,7 @@ quit</programlisting>
<para>For example, suppose you are running <quote>make
buildworld</quote>, and the compile fails while trying to
compile <filename>ls.c</filename> in to
compile <filename>ls.c</filename> into
<filename>ls.o</filename>. If you then run <quote>make
buildworld</quote> again, and the compile fails in the same
place then this is a broken build -- try updating your sources
@ -4223,7 +4223,7 @@ Timecounter "TSC" frequency 595573479 Hz</screen>
kern.timecounter.hardware: TSC</screen>
<para>The BIOS may modify the TSC clock&mdash;perhaps to change the
speed of the processor when running from batteries, or going in to
speed of the processor when running from batteries, or going into
a power saving mode, but FreeBSD is unaware of these adjustments,
and appears to gain or lose time.</para>
@ -11492,7 +11492,7 @@ raisechar=^^</programlisting>
other vital component is an atomic power-plant, I guess
that illustrates the age of the book.</para>
<para>Parkinson shows how you can go in to the board of
<para>Parkinson shows how you can go into the board of
directors and get approval for building a multi-million or
even billion dollar atomic power plant, but if you want to
build a bike shed you will be tangled up in endless

View file

@ -99,7 +99,7 @@
<sect2>
<title>Sectional elements</title>
<para>An HTML document is normally split in to two sections. The first
<para>An HTML document is normally split into two sections. The first
section, called the <emphasis>head</emphasis>, contains
meta-information about the document, such as its title, the name of
the author, the parent document, and so on. The second section, the
@ -314,7 +314,7 @@
<para>You can indicate that text should be shown to the user exactly
as it is in the file. Typically, this means that the text is shown
in a fixed font, multiple spaces are not merged in to one, and line
in a fixed font, multiple spaces are not merged into one, and line
breaks in the text are significant.</para>
<para>In order to do this, wrap the content in the
@ -434,7 +434,7 @@
<para>Use:</para>
<programlisting><![ CDATA [<p>On a 3x3 grid, the top left block is a 2x2 set of
cells merged in to one. The other cells are normal.</p>
cells merged into one. The other cells are normal.</p>
<table>
<tr>
@ -444,7 +444,7 @@
</tr>
<tr>
<!-- Because the large cell on the left merges in to
<!-- Because the large cell on the left merges into
this row, the first <td> will occur on its
right -->
@ -1473,7 +1473,7 @@ main(void)
the user types in a command, the user gets a response back, they
type in another command, and so on.</para>
<para>A number of distinct elements and entities come in to play
<para>A number of distinct elements and entities come into play
here.</para>
<variablelist>
@ -2431,7 +2431,7 @@ IMAGES+= fig3.png
<sect3>
<title>Images and chapters in subdirectories</title>
<para>You must be careful when you separate your documentation in to
<para>You must be careful when you separate your documentation into
smaller files (see <xref linkend="sgml-primer-include-using-gen-entities">) in
different directories.</para>

View file

@ -1249,7 +1249,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
</step>
<step>
<para>Load <filename>example.html</filename> in to your web
<para>Load <filename>example.html</filename> into your web
browser, and confirm that the
<filename>para<replaceable>n</replaceable>.sgml</filename> files
have been included in <filename>example.html</filename>.</para>
@ -1306,7 +1306,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
</step>
<step>
<para>Load <filename>example.html</filename> in to your web
<para>Load <filename>example.html</filename> into your web
browser, and confirm that the
<filename>para<replaceable>n</replaceable>.sgml</filename> files
have been included in <filename>example.html</filename>.</para>

View file

@ -36,7 +36,7 @@
<para>The <filename>doc/</filename> tree is organised in a particular
fashion, and the documents that are part of the FDP are in turn organised
in a particular fashion. The aim is to make it simple to add new
documentation in to the tree and:</para>
documentation into the tree and:</para>
<orderedlist>
<listitem>
@ -124,7 +124,7 @@
<seg><filename>books</filename></seg>
<seg>Documentation marked up as a DocBook <sgmltag>book</sgmltag> (or
equivalent). Book length, and broken up in to chapters. Normally
equivalent). Book length, and broken up into chapters. Normally
available as both one large HTML file (for people with fast
connections, or who want to print it easily from a browser) and
as a collection of linked, smaller files.</seg>
@ -238,7 +238,7 @@
<para>In earlier versions of the Handbook the files were stored in
the same directory as <filename>book.sgml</filename>, and named
after the value of the <literal>id</literal> attribute on the
file's <sgmltag>chapter</sgmltag> element. Moving them in to
file's <sgmltag>chapter</sgmltag> element. Moving them into
separate directories prepares for future plans for the Handbook.
Specifically, it will soon be possible to include images in each
chapter. It makes more sense for each image to be stored in a

View file

@ -87,7 +87,7 @@
</step>
<step>
<para>Change in to the <filename>www</filename> directory, and
<para>Change into the <filename>www</filename> directory, and
run the &man.make.1; <maketarget>links</maketarget> target, to
create the necessary symbolic links.</para>
@ -96,7 +96,7 @@
</step>
<step>
<para>Change in to the <filename>en</filename> directory, and run
<para>Change into the <filename>en</filename> directory, and run
the &man.make.1; <maketarget>all</maketarget> target, to create
the web pages.</para>
@ -126,7 +126,7 @@
</step>
<step>
<para>If you have previously installed the web pages in to the same
<para>If you have previously installed the web pages into the same
directory the install process will not have deleted any old or
outdated pages. For example, if you build and install a new copy
of the site every day, this command will find and delete all

View file

@ -249,7 +249,7 @@
<answer>
<para>First, make sure your translation is organised properly. This
means that it should drop in to the existing documentation tree and
means that it should drop into the existing documentation tree and
build straight away.</para>
<para>Currently, the FreeBSD documentation is stored in a top level

View file

@ -1157,7 +1157,7 @@ MASTER_SITE_SUBDIR= applications</programlisting>
<para>The dependency is checked from within the
<maketarget>install</maketarget> target. Also, the name of the
dependency is put in to the package so that
dependency is put into the package so that
<command>pkg_add</command> will automatically install it if it is
not on the user's system. The <replaceable>target</replaceable>
part can be omitted if it is the same as
@ -2201,7 +2201,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
among several ports or have to write to one of the above files (see
<link linkend="porting-wrkdir">writing to places other than
<makevar>WRKDIR</makevar></link> for why it is a bad idea to write
directly in to the <filename>pkg-<replaceable>*</replaceable></filename> subdirectory).</para>
directly into the <filename>pkg-<replaceable>*</replaceable></filename> subdirectory).</para>
<para>Here is a list of variable names and their default
values. (<makevar>PKGDIR</makevar> defaults to