[Reproducible-commits] [blog] 01/01: Fix minor typos.

[Vagrant Cascadian]

This is an automated email from the git hooks/post-receive script.

vagrant pushed a commit to branch master
in repository blog.

commit 24fdad660df558d9aa6372fa2bdeaef8ea0c7ee5
Author: Vagrant Cascadian <vagrant at debian.org>
Date:   Mon Aug 22 13:59:28 2016 -0700

    Fix minor typos.
---
 drafts/69.mdwn | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drafts/69.mdwn b/drafts/69.mdwn
index f83c609..045fb6b 100644
--- a/drafts/69.mdwn
+++ b/drafts/69.mdwn
@@ -180,9 +180,9 @@ Debian related:
 
 The last change probably will have an impact you will see: your package might become unreproducible in *unstable* and this will be shown on [tracker.debian.org](https://tracker.debian.org), while it will still be reproducible in *testing*.
 
-We've done this, because we think reproducible builds are possible with arbitrary build pathes. But: we don't think those are a realistic goal for *stretch*, where we still recommend to use ´.buildinfo´ to record the build patch and then do rebuilds using that path.
+We've done this, because we think reproducible builds are possible with arbitrary build paths. But: we don't think those are a realistic goal for *stretch*, where we still recommend to use ´.buildinfo´ to record the build patch and then do rebuilds using that path.
 
-We are doing this, because besides doing theoretical groundwork we also have a practial goal: enable users to indipendantly verify builds. And if they only can do this with a fixed path, so be it. For now :)
+We are doing this, because besides doing theoretical groundwork we also have a practical goal: enable users to independently verify builds. And if they only can do this with a fixed path, so be it. For now :)
 
 For future reference, when we enabled build path variation on Saturday, August 20th 2016, the number for *unstable* were:
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/blog.git