diff options
| author | Aurelien Foret <aurelien@archlinux.org> | 2005-10-05 09:55:00 +0200 |
|---|---|---|
| committer | Aurelien Foret <aurelien@archlinux.org> | 2005-10-05 09:55:00 +0200 |
| commit | b7e7bc352abf9e60bf670557767539f1633389dd (patch) | |
| tree | 398e283ca9b165e60dbd3b9319cd60e7e3feb951 | |
| parent | 033b318f8cf73a0f2b6cf6f0275be04d86ca44e7 (diff) | |
| download | pacman-b7e7bc352abf9e60bf670557767539f1633389dd.tar.gz pacman-b7e7bc352abf9e60bf670557767539f1633389dd.tar.xz | |
Fixed some typos
| -rw-r--r-- | README | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -89,7 +89,7 @@ Last, but not least, the handle holds a _unique_ transaction object. [TRANSACTION] (see trans.c, and also alpm.c)
-The transaction sturcture permits easy manipulations of several package
+The transaction sturcture permits easy manipulations of several packages
at a time (i.e. adding, upgrade and removal operations).
A transaction can be initiatied with a type (ADD, UPGRADE or REMOVE),
@@ -140,9 +140,9 @@ Compared to pacman 2.9, there is now one cache object connected to each database object.
There are both a package and a group cache.
The cache is loaded only on demand (i.e the cache is loaded the first
-time data from it should used).
+time data from it should be used).
-Note: the cache of a database is always destroyed by the library after
+Note: the cache of a database is always updated by the library after
an operation changing the database content (adding and/or removal of
packages).
Beware frontends ;)
|