Merge pull request #135 from jbampton/fix-spelling

Fix spelling

Author: robmoffat

docs/thinking/Risk-First-Diagrams.md

@@ -83,7 +83,7 @@ There are [all kinds of risks](/risks/Risk-Landscape) we face in life and we att
 
 As well as considering Risk-First diagrams to be like the [Stimulus-Response Model](https://en.wikipedia.org/wiki/Stimulus–response_model), you could also think in terms of [functional programming](https://en.wikipedia.org/wiki/Functional_programming), which might be more familiar to us as software developers.  
 
-We are _tranforming_ an input condition (on the left) into an _output_ condition (on the right) by way of a function (the action we take, in the middle).  
+We are _transforming_ an input condition (on the left) into an _output_ condition (on the right) by way of a function (the action we take, in the middle).  
 
 ## Other Elements
 

src/components/front/HomeSection/index.js

@@ -2,7 +2,7 @@ import React from 'react';
 import styles from './styles.module.css'
 import MonoIcon from '../MonoIcon'
 
-// left, right panels, a call to action adn a footer icon
+// left, right panels, a call to action and a footer icon
 export default ({children, alt, reverse}) => {
 	return (
 		<section className={alt ? styles.homeSectionAlt : styles.homeSection}>

src/components/front/HomeSection2/index.js

@@ -2,7 +2,7 @@ import React from 'react';
 import styles from './styles.module.css'
 import MonoIcon from '../MonoIcon'
 
-// title, central panel, a call to action adn a footer icon
+// title, central panel, a call to action and a footer icon
 export default ({ children, alt }) => {
 	return (
 		<section className={alt ? styles.homeSectionAlt : styles.homeSection}>

unused_content/complexity/End-Of-Complexity.md

@@ -31,7 +31,7 @@ Faced with this baffling choice, what are developers to do?  Jono Bacon, at the
 
 The current approach developers apply all the time is the [Lindy Effect](https://en.wikipedia.org/wiki/Lindy_effect):  assume that any software that has been around x years will be around another x years.  This really restricts the search-space, but means you're not on the bleeding edge. (Often a good thing).  
 
-A variation on this is social status- indicated by GitHub stars or questions on Stack Overflow, or the number of conferences about that thing.  
+A variation on this is social status indicated by GitHub stars or questions on Stack Overflow, or the number of conferences about that thing.  
 
 We're kind of getting by with this - but it still gets harder all the time.  There are just too many options to even _discover_ them all these days.  It's more likely that we're using a tool X due to some historical accident rather than any reasoned analysis of its strengths or weaknesses.
 

unused_content/complexity/Hierarchies.md

@@ -16,7 +16,7 @@ tweet: yes
 
 ##### "Hierarchies are the wheel we're happy to re-invent over and over and over again."
 
-Have you noticed just how prevalent the idea of _heirarchy_ is in software?  By hierarchy, I mean a general pattern of _connectedness_, where a _parent_ has some _children_, who, in turn, may each have some further children, and so on.
+Have you noticed just how prevalent the idea of _hierarchy_ is in software?  By hierarchy, I mean a general pattern of _connectedness_, where a _parent_ has some _children_, who, in turn, may each have some further children, and so on.
 
 This is a really popular pattern.  But what's odd about it is that we seem to re-invent it over and over again in software.