[blog] 01/02: Cosmetic changes, etc. to week 78.

[Chris Lamb]

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

lamby pushed a commit to branch master
in repository blog.

commit 52e303d29fd4d98235b595303cde52d5e89de8fa
Author: Chris Lamb <lamby at debian.org>
Date:   Mon Oct 24 17:09:05 2016 +0100

    Cosmetic changes, etc. to week 78.
---
 drafts/78.mdwn | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/drafts/78.mdwn b/drafts/78.mdwn
index bc9b7c5..2c619f4 100644
--- a/drafts/78.mdwn
+++ b/drafts/78.mdwn
@@ -6,7 +6,7 @@ Builds](https://wiki.debian.org/ReproducibleBuilds) effort between Sunday Octobe
 Media coverage
 --------------
 
-- Chris Lamb presented a talk at [Software Freedom Kosovo](http://sfk.flossk.org/sfk16/) on reproducible builds on Saturday 22nd October.
+- Chris Lamb presented at [Software Freedom Kosovo](http://sfk.flossk.org/sfk16/) on reproducible builds on Saturday 22nd October.
 
 Upcoming events
 ---------------
@@ -16,9 +16,9 @@ Upcoming events
 buildinfo.debian.net
 --------------------
 
-For our goal of enabling everyone to rebuild everything reproducibly, we have the concept of ``.buildinfo`` files, which generally spoken describe the environment, the inputs and the outputs and in the Debian case are available once per package/architecture/version tuple. We anticipate the next dpkg upload to sid will create such ``.buildinfo`` files by default - and while it's clear that we need to teach dak to deal with them (see [[!bug 763822]]), it's not actually clear how to handle  [...]
+To enable everyone to rebuild everything reproducibly, we have the concept of ``.buildinfo`` files which generally describe the environment used for a particular build; the inputs and the outputs and, in the Debian case, are available per per package/architecture/version tuple. We anticipate the next ``dpkg`` upload to sid will create such ``.buildinfo`` files by default  and while it's clear that we need to teach dak to deal with them (see [[!bug 763822]]), it's not actually clear how t [...]
 
-So Chris Lamb has started development on an [highly proof-of-concept ``.buildinfo`` server](http://buildinfo.debian.net/) licensed under the GNU AGPLv3. [Source](https://github.com/lamby/buildinfo.debian.net)
+To this end, Chris Lamb has started development on an [highly proof-of-concept ``.buildinfo`` server](http://buildinfo.debian.net/) licensed under the GNU AGPLv3. [Source](https://github.com/lamby/buildinfo.debian.net)
 
 
 Reproducible work in other projects
@@ -88,8 +88,8 @@ tests.reproducible-builds.org
 Misc.
 -----
 
-Our [poll to find a good time for an IRC meeting](http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20161017/007298.html) is still running until Tuesday, October 25st; so please real soon now.
+Our [poll to find a good time for an IRC meeting](http://lists.alioth.debian.org/pipermail/reproducible-builds/Week-of-Mon-20161017/007298.html) is still running until Tuesday, October 25st; please reply as soon as possible.
 
-We need a logo! Some [ideas and requirements for a Reproducible Builds logo](https://wiki.debian.org/ReproducibleBuilds/Logo) have been documented in the wiki. Help much welcome, also by just forwarding this information!
+We need a logo! Some [ideas and requirements for a Reproducible Builds logo](https://wiki.debian.org/ReproducibleBuilds/Logo) have been documented in the wiki. Contributions very welcome, even if simply by forwarding this information.
 
 This week's edition was written by Chris Lamb & Holger Levsen and reviewed by a bunch of Reproducible Builds folks on IRC.

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