British English -> American English:

* organisation -> organization
* organise -> organize
* optimisation -> optimization
* optimises -> optimizes
* artefacts -> artifacts

Spelling:
* asociated -> associated
This commit is contained in:
Chern Lee 2001-08-22 18:12:57 +00:00
parent a75ba4dd47
commit b3359c0e63
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10434

View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.94 2001/08/20 21:46:50 nik Exp $
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.95 2001/08/21 23:42:44 nik Exp $
-->
<chapter id="install">
@ -1106,9 +1106,9 @@ Mounting root from ufs:/dev/md0c
information on the disk.</para>
<sect2>
<title>Disk Organisation</title>
<title>Disk Organization</title>
<para>The smallest unit of organisation that FreeBSD uses to find files
<para>The smallest unit of organization that FreeBSD uses to find files
is the filename. Filenames are case-sensitive, which means that
<filename>readme.txt</filename> and <filename>README.TXT</filename>
are two separate files. FreeBSD does not use the extension
@ -1118,7 +1118,7 @@ Mounting root from ufs:/dev/md0c
<para>Files are stored in directories. A directory may contain no
files, or it may contain many hundreds of files. A directory can also
contain other directories, allowing you to build up a hierarchy of
directories within one another. This makes it much easier to organise
directories within one another. This makes it much easier to organize
your data.</para>
<para>Files and directories are referenced by giving the file or
@ -1268,12 +1268,12 @@ Mounting root from ufs:/dev/md0c
</listitem>
<listitem>
<para>FreeBSD automatically optimises the layout of files on a
<para>FreeBSD automatically optimizes the layout of files on a
filesystem, depending on how the filesystem is being used. So a
filesystem that contains many small files that are written
frequently will have a different optimisation to one that contains
frequently will have a different optimization to one that contains
fewer, larger files. By having one big filesystem this
optimisation breaks down.</para>
optimization breaks down.</para>
</listitem>
<listitem>
@ -1322,7 +1322,7 @@ Mounting root from ufs:/dev/md0c
currently being used to the swap space, and moves it back in (moving
something else out) when it needs it.</para>
<para>Some partitions have certain conventions asociated with
<para>Some partitions have certain conventions associated with
them.</para>
<informaltable frame="none">
@ -1626,7 +1626,7 @@ Mounting root from ufs:/dev/md0c
<para>The second section shows the slices that are currently on the
disk, where they start and end, how large they are, the name FreeBSD
gives the, and their description and sub-type. This example shows two
small unused slices, which are artefacts of disk layout schemes on the
small unused slices, which are artifacts of disk layout schemes on the
PC. It also shows one large FAT slice, which almost certainly appears
as <devicename>C:</devicename> in DOS / Windows, and an extended
slice, which may contain other drive letters for DOS / Windows.</para>