From 0c179eea47c346794935565be3502985ab65cf3c Mon Sep 17 00:00:00 2001
From: Patrick Spek <p.spek@tyil.nl>
Date: Thu, 23 Aug 2018 15:03:57 +0200
Subject: Reword first paragraph of Releasing a Perl 6 module

---
 _posts/2018-08-15-the-perl-conference-in-glasgow.adoc | 17 +++++++++--------
 1 file changed, 9 insertions(+), 8 deletions(-)

(limited to '_posts/2018-08-15-the-perl-conference-in-glasgow.adoc')

diff --git a/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc b/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
index 28ffdff..f65fab9 100644
--- a/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
+++ b/_posts/2018-08-15-the-perl-conference-in-glasgow.adoc
@@ -90,19 +90,20 @@ like Tux's `Text::CSV` runs.
 
 The speaker starts off with detailing the platform which most Perl 6 modules
 use to host their code repository, GitHub. He also touched upon automated
-testing using Travis and AppVeyor.  Personally, I prefer GitLab over GitHub, as
-they have much better testing functionality, and they actually release their
-own platform as an open source package. I'd like more GitLab love from the
-community and speakers as well if possible. This would also make the speaker's
-CI configuration simpler, for which he currently uses a `.travis.yml` file.
-This requires him to build Perl 6 from source every test run, wasting quite a
-lot of time.
+testing using Travis and AppVeyor. It was good to show how to make use of
+these, as automated testing oftentimes stops unintended bugs from reaching end
+users. But, I personally prefer GitLab over GitHub, as they have much better
+testing functionality, and they actually release their own platform as an open
+source package. I'd like more GitLab love from the community and speakers as
+well if possible. This would also make the speaker's CI configuration simpler,
+for which he currently uses a `.travis.yml` file.  This requires him to build
+Perl 6 from source every test run, wasting quite a lot of time.
 
 It was also noted that there's a module to help you set up this module
 skeleton, `mi6`. The speaker also noted that it doesn't seem to add much once
 you know how a Perl 6 module is organized, and I tend to agree with this.
 Actually, I made a module precisely because I agree with him here,
-`App::Assixt`.  This module intends to smoothen the entire course of module
+`App::Assixt`. This module intends to smoothen the entire course of module
 development, not just the creation of a skeleton file. It will take care of
 keeping your `META6.json` up to date, and ease uploading your module to CPAN as
 well.
-- 
cgit v1.1

