aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVincent Legoll <vincent.legoll@gmail.com>2020-04-05 15:22:46 +0200
committerChristopher Baines <mail@cbaines.net>2020-04-05 21:07:35 +0100
commitb2ec5474344d4ff54743e00c2c81279cfc2b5491 (patch)
tree844c48151329a0b8f1462beebc46906b7f7892d1
parente514471fc9a541089aa406a19cceec3479926fa1 (diff)
downloaddata-service-b2ec5474344d4ff54743e00c2c81279cfc2b5491.tar
data-service-b2ec5474344d4ff54743e00c2c81279cfc2b5491.tar.gz
Fix typos in README
Signed-off-by: Christopher Baines <mail@cbaines.net>
-rw-r--r--README4
1 files changed, 2 insertions, 2 deletions
diff --git a/README b/README
index 1638a92..03bb0d3 100644
--- a/README
+++ b/README
@@ -20,8 +20,8 @@ the history of the derivations for a package over recent Guix revisions, it
could take some time until you have the information you're looking for.
However, with the Guix Data Service, this information can be gathered
-continuously, and stored in a a manor that makes these kind of queries much
-quicker to answer. By storing data abount multiple Guix revisions in a SQL
+continuously, and stored in a way that makes these kind of queries much
+quicker to answer. By storing data about multiple Guix revisions in a SQL
database (PostgreSQL), it becomes possible to quickly compare the data for
different revisions. By configuring the Guix Data Service to listen for
changes in the Guix Git repository, the database can be kept up to date.