typos

7 files changed, 12 insertions, 12 deletions

diff --git a/posts/2016/elm-everything-broken.md b/posts/2016/elm-everything-broken.md
index a9978d1..58b848f 100644
--- a/posts/2016/elm-everything-broken.md
+++ b/posts/2016/elm-everything-broken.md
@@ -321,7 +321,7 @@ still allowing rapid evolution of a package "ecosystem". Cargo was designed by
 feeling are usually that system-wide package managers (like Debian's `apt`) are
 underappreciated by many young-but-not-bleeding-edge projects, but acknowledge
 that there probably is also a need for higher tempo cross-platform project
-dependency mangement for non-library projects (eg, desktop applications and web
+dependency management for non-library projects (eg, desktop applications and web
 apps).
 
 Ironically (given the difficulty I had installing it), the Elm language's
@@ -348,7 +348,7 @@ For [example](https://gist.github.com/badboy/a302dd0c9020e5759240):
             defaultOptions : Html.Events.Options
             onWithOptions : String -> Html.Events.Options -> Json.Decode.Decoder a -> (a -> Signal.Message) -> Html.Attribute
 
-This API change information is then used to *[programatically enforce][7]* the
+This API change information is then used to *[programmatically enforce][7]* the
 semantic versioning rules for submissions to the Elm language library archive
 and prevent a whole class of simple but annoying breakages due to unexpected
 API changes. It can't detect *every* breaking change (eg, those which are
diff --git a/posts/2016/juliacon.md b/posts/2016/juliacon.md
index 52751a9..c0e916a 100644
--- a/posts/2016/juliacon.md
+++ b/posts/2016/juliacon.md
@@ -287,7 +287,7 @@ difficult 1.0 process first. It was mentioned that 0.6 would be the last of the
 things should generally be backwards compatible.
 
 Separate from Stefan's talk, there was a short overview of progress on the next
-iteration of the Julia package and dependency manger, called Pkg3. The goals
+iteration of the Julia package and dependency manager, called Pkg3. The goals
 were described as "a mash-up of virtualenv and cargo": virtualenv is a tool for
 isolating per-application dependencies and toolchains in Python, and Cargo is
 is the Rust dependency manager and build tool (which is also used in a
diff --git a/posts/2016/new-server-2016.md b/posts/2016/new-server-2016.md
index 8f2245b..8eb5449 100644
--- a/posts/2016/new-server-2016.md
+++ b/posts/2016/new-server-2016.md
@@ -47,7 +47,7 @@ settled yet: I haven't moved email, and I'm not sure if I'll stick with
 
 [pelican]:  http://blog.getpelican.com/
 [linode]:   https://www.linode.com
-[digial ocean]: https://digitalocean.com
+[digital ocean]: https://digitalocean.com
 [infra]: http://git.bnewbold.net/infra/
 [mediagoblin]: http://mediagoblin.org
 
diff --git a/posts/2019/three_spirits_libre_software.md b/posts/2019/three_spirits_libre_software.md
index ecd12ff..e6b3b13 100644
--- a/posts/2019/three_spirits_libre_software.md
+++ b/posts/2019/three_spirits_libre_software.md
@@ -25,7 +25,7 @@ the goals and vision members are pursuing. I feel like I spend a lot of time
 re-telling my own version of "what we're really trying to achieve here" and
 disclaiming strawman arguments. Sometimes these discussions are with critics,
 but just as often they are with disillusioned contributors who feel like they
-are loosing the fight. Having these in a written form is something coherent to
+are losing the fight. Having these in a written form is something coherent to
 point to, and also gives me a framework to gauge progress (or lack there of) in
 the future.
 
diff --git a/posts/biblio-metadata-collections.md b/posts/biblio-metadata-collections.md
index d7f8713..91bafe8 100644
--- a/posts/biblio-metadata-collections.md
+++ b/posts/biblio-metadata-collections.md
@@ -12,7 +12,7 @@ I've recently been lucky enough to start working on a new big project at the
 [Internet Archive][]: collecting, indexing, and expanding access to research
 publications and datasets in the open world. This is perhaps *the* original
 goal of networked information technology, and thanks to a decade of hard
-work by the Open Access movement it feels like intertia
+work by the Open Access movement it feels like inertia
 [is building][nature-elsevier] towards this one small piece of "universal
 access to all knowledge".
 
diff --git a/posts/merkle-design.md b/posts/merkle-design.md
index b388dab..707e194 100644
--- a/posts/merkle-design.md
+++ b/posts/merkle-design.md
@@ -15,7 +15,7 @@ My interest in these systems is as infrastructure for the commons of cultural
 and intellectual works: making it cheap and easy to publish content that
 becomes easily accessible and woven in to the web of reference and derivative
 works. From my work at the Internet Archive collecting Open Access
-publications and datasets, I have a particular interest in dereferencable links
+publications and datasets, I have a particular interest in dereferenceable links
 (and/or citations) that will work in the future,
 
 [wp-merkle]: https://en.wikipedia.org/wiki/Merkle_tree
@@ -27,7 +27,7 @@ system:
 the wire.  If every distinct file can be identified by only a single,
 reproducible name, then discovery, indexing, and de-duplicaiton is made easier.
 If the same file can end up with different names, then that file might be
-transfered or stored separately by default; this creates pressure for the
+transferred or stored separately by default; this creates pressure for the
 application layer to support the concept of "many identifiers for the same
 file", and requires additional coordination at scale.
 
@@ -94,7 +94,7 @@ folks love to think about re-inventing "everything" on top of such a system. I
 think this is because git supplies specific semantic features people love,
 while being deeply entangled with files and file systems. Computer engingeering
 is All About Files, and git is both made out of files (look in .git; it's
-simple files and directories all the way down!) and accomodating files.
+simple files and directories all the way down!) and accommodating files.
 
 Consider:
 
diff --git a/posts/modelthing-background.md b/posts/modelthing-background.md
index ae79211..51bd2db 100644
--- a/posts/modelthing-background.md
+++ b/posts/modelthing-background.md
@@ -4,7 +4,7 @@ Date: 2020-06-28
 Tags: modelthing
 Status: draft
 
-This post describes the potential for collaborative infrastructure to agument
+This post describes the potential for collaborative infrastructure to augment
 human research and understanding using mathematical models. These models,
 consisting of symbolic equations which are semantic and machine-readable, have
 historically been "unreasonably effective" at describing the natural world. A
@@ -23,7 +23,7 @@ to answer.
 Much of my university (undergraduate) time studying physics was spent exploring
 computational packages and computer algebra systems to automate math.  These
 included general purpose computer algebra or numerical computation systems like
-Mathematica, MATLAB, Numerical Recipies in C, SciPy, and Sage, as well as
+Mathematica, MATLAB, Numerical Recipes in C, SciPy, and Sage, as well as
 real-time data acquisition or simulation systems like LabView, ROOT, Geant4,
 and EPICS. I frequently used an online system called Hyperphysics to refresh my
 memory of basic physics and make quick calculations of things like Rayleigh
@@ -52,7 +52,7 @@ learning format will not be best for everybody.
 </div>
 
 A particularly influential experience late in my education was taking a course
-on classical mechanics using the Scheme programing language, taught by the
+on classical mechanics using the Scheme programming language, taught by the
 authors of "Structure and Interpretation of Classical Mechanics" (SICM). The
 pedagogy of this course really struck a chord with me. Instead of learning how
 to operate a complex or even proprietary software black box, students learned