Fix typos

Author: algonell

_posts/2017-10-11-edition-32.markdown

@@ -345,7 +345,7 @@ have. It would be as if the worktree was partitioned into separate
 using submodule commit hashes. Importantly, it should be possible for
 the user's local server repo (is there a word for this 'on-server
 personal fork'?) to also be a narrow clone, as distinct from the
-golden server which would alway a full width, and able to serve narrow
+golden server which would always a full width, and able to serve narrow
 packs.
 
 The other aspect of Git would be to include practical user examples on

_posts/2017-11-22-edition-33.markdown

@@ -89,7 +89,7 @@ Jonathan Nieder answered:
 > want to switch to LF endings, in which case I suggest the "single
 > fixup commit" strategy.
 
-He suggested though to declare explicitely all the files as non text
+He suggested though to declare explicitly all the files as non text
 files in `.gitattributes` using the `-text` flag, so that Git will not be
 tempted to change line endings.