summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2017-03-20 15:02:38 +0100
committerLudovic Courtès <ludo@gnu.org>2017-03-20 15:02:38 +0100
commit65bba97d97bbdfa9cc604b8cadbd9fffb7e2b3a2 (patch)
tree2c64cbf0be2286303d384830c92e4d020ab38ed7
parent93e333ea9b5331ca7c04d847d92cb26a1216f6c1 (diff)
downloadguix-artwork-65bba97d97bbdfa9cc604b8cadbd9fffb7e2b3a2.tar
guix-artwork-65bba97d97bbdfa9cc604b8cadbd9fffb7e2b3a2.tar.gz
website: pack: Fix typo.
* website/posts/creating-bundles-with-guix-pack.md: Fix typo.
-rw-r--r--website/posts/creating-bundles-with-guix-pack.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/website/posts/creating-bundles-with-guix-pack.md b/website/posts/creating-bundles-with-guix-pack.md
index 26d2c5f..f5a2fac 100644
--- a/website/posts/creating-bundles-with-guix-pack.md
+++ b/website/posts/creating-bundles-with-guix-pack.md
@@ -210,7 +210,7 @@ wonders.
Packs themselves are reproducible bit-by-bit. If you know the Guix
commit that was used to build a given pack, you can thus run the same
`guix pack` command on another machine and verify that you get the exact
-same tarball. Currently not 100% of the packages Guix provide are
+same tarball. Currently not 100% of the packages Guix provides are
reproducible bit-by-bit; we’re getting closer to that goal though, in
part due to the fact that Guix builds are isolated by default, and also
thanks to the efforts of everyone in the