_posts: grammar tweaks

2 files changed, 9 insertions, 14 deletions

diff --git a/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md b/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
index 701c323..0fd6c30 100644
--- a/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
+++ b/_posts/2015-07-03-std-call-once-bug-in-visual-studio-2012-2013.md
@@ -2,15 +2,10 @@
 title: std::call_once bug in Visual Studio 2012/2013
 layout: post
 excerpt: >
-  In this post I will describe a neat bug I've stumbled upon in the C++
+  In this post I will describe a nasty bug I've stumbled upon in the C++
   Standard Library implementation shipped with Microsoft Visual Studio
   2012/2013.
 ---
-{{ page.excerpt }}
-
-Introduction
-------------
-
 I've recently come across a nasty standard library bug in the implementation
 shipped with Microsoft Visual Studio 2012/2013.
 [StackOverflow was of no help], so I had to somehow report the bug to the
diff --git a/_posts/2017-01-07-building-boost.md b/_posts/2017-01-07-building-boost.md
index 5e71334..ae8221a 100644
--- a/_posts/2017-01-07-building-boost.md
+++ b/_posts/2017-01-07-building-boost.md
@@ -26,18 +26,18 @@ Excerpts from shell sessions in this post feature a few different commands
 besides Boost's `b2` and `cmake`, like `cd` and `cat`.
 They are used to hint at my personal directory layout, display various
 auxiliary files, etc.
-Windows' `cd`, for example, simply prints current working directory; Cygwin's
-`pwd` serves the same purpose.
+Windows' `cd`, for example, simply prints the current working directory;
+Cygwin's `pwd` serves the same purpose.
 `cat` is used to display files.
-Windows' command prompts are denoted with `>`s at beginning of each line;
+Windows' command prompts are denoted with `>`s at the beginning of each line;
 Cygwin's — with `$`s.
 
 Visual Studio
 -------------
 
-Statically-linked Boost libraries are built by default, both the debug and the
-release versions of them.
-While it is required to keep x86/x64 libraries in different directories (to
+Statically-linked Boost libraries are built, both the debug and the release
+versions of them (these are default settings).
+While it is required to keep x86 and x64 libraries in different directories (to
 avoid file name clashes), it's not necessary to separate debug libraries from
 their release counterparts, because that information is actually encoded in
 file names (the "gd" suffix).
@@ -129,7 +129,7 @@ $ ./b2 toolset=gcc-mingw              \
 Notice the two major differences from the x86 example:
 
 * the addition of `address-model=64` (as in the example for Visual Studio),
-* a different "user" configuration file, pointing to `x86_64-w64-mingw32-g++`
+* the different "user" configuration file, pointing to `x86_64-w64-mingw32-g++`
 instead of `i686-w64-mingw32-g++`.
 
 Again, as in the example for Visual Studio, a different "staging" directory
@@ -197,7 +197,7 @@ D:\workspace\build\test_project\msvc\x86
 ### Cygwin & MinGW-w64
 
 Examples below only apply to debug CMake builds.
-Notice that, contrary to the Visual Studio examples above, debug *and* release
+Notice that, contrary to the Visual Studio examples above, debug and release
 builds must be kept in separate directories.
 You may also want to adjust the paths.