01/01: website: pack: Update blog post.

[Ludovic Courtès]

civodul pushed a commit to branch master
in repository guix-artwork.

commit 93e333ea9b5331ca7c04d847d92cb26a1216f6c1
Author: Ludovic Courtès <address@hidden>
Date:   Mon Mar 20 14:45:49 2017 +0100

    website: pack: Update blog post.
    
    * website/posts/creating-bundles-with-guix-pack.md: Take into account
    comments by Ricardo.
---
 website/posts/creating-bundles-with-guix-pack.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/website/posts/creating-bundles-with-guix-pack.md 
b/website/posts/creating-bundles-with-guix-pack.md
index d24ef86..26d2c5f 100644
--- a/website/posts/creating-bundles-with-guix-pack.md
+++ b/website/posts/creating-bundles-with-guix-pack.md
@@ -1,5 +1,5 @@
 title: Creating bundles with guix pack
-date: 2017-03-20 14:00
+date: 2017-03-20 14:45
 author: Ludovic Courtès
 tags: pack bundles
 ---
@@ -34,7 +34,7 @@ So how does it work?  The basic idea is simple: you type
 guix pack guile
 ```
 
-and you the command returns in `/gnu/store` a good old tarball that
+and the command returns in `/gnu/store` a good old tarball that
 contains binaries for Guile and all its dependencies.  If you run, say,
 
 ```
@@ -121,7 +121,8 @@ GNU/Linux on ARMv7:
 guix pack --target=arm-linux-gnueabihf guile
 ```
 
-… while the command below creates a pack with binaries for MinGW:
+… while the command below creates a pack with Windows binaries using the
+MinGW cross-compiler:
 
 ```
 guix pack --target=i686-w64-mingw32 guile