[PATCH] trivial typo fixes

Frodo Baggins frodo.drogo at gmail.com
Sat Sep 1 11:15:16 UTC 2007


---
 doc/API |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/API b/doc/API
index 00ee0f4..c62ff75 100644
--- a/doc/API
+++ b/doc/API
@@ -59,7 +59,7 @@ libparted provides an API capable of man
 the filesystems on them.

 The main motivation for separating the back-end into a separate library was
-to encourage different GNU/Linux distributions to encorporate their own
+to encourage different GNU/Linux distributions to incorporate their own
 customized front-end into the install process.

 This documents the API -- not the implementation details of libparted.
@@ -120,7 +120,7 @@ TIMER                       a progress meter.  It is an enti
 --------------
 libparted has a fairly object-oriented design.  The most important objects are:

-PedArchitecture                describes support for an "archicture",
which is sort
+PedArchitecture                describes support for an
"architecture", which is sort
                        of like "operating system", but could also be,
                        for example, another libparted environment, EVMS, etc.
 PedConstraint          a constraint on the geometry of a partition
@@ -128,7 +128,7 @@ PedDevice           a storage device
 PedDisk                        a device + partition table
 PedFileSystem          a filesystem, associated with a PedGeometry, NOT a
                        PedPartition.
-PedGeometry            a continious region on a device
+PedGeometry            a continuous region on a device
 PedPartition           a partition (basically PedGeometry plus some attributes)
 PedTimer               a timer keeps track of progress and time

@@ -238,7 +238,7 @@ For more information on the maths, see t
 containing proofs above ped_alignment_intersect() in libparted/natmath.c

 The restrictions on the location of the start and end are in the form of
-PedGeometry objects -- continous regions in which the start and end must lie.
+PedGeometry objects -- continuous regions in which the start and end must lie.
 Obviously, these restrictions are also closed under intersection.

 The other restriction -- the minimum size -- is also closed under intersection.
--
1.4.3.4



More information about the parted-devel mailing list