Merge pull request #2 from zachgrayio/patch-1

Update WhySwiftForTensorFlow.md - typo fix

docs/WhySwiftForTensorFlow.md

@@ -8,7 +8,7 @@ That said, while our choice of language was guided by our specific project goals
 
 ### How we got here
 
-As discussed in the [design overview document](DesignOverview.md) our project goal goal is to improve usability of TensorFlow.  We quickly realized that our core [static analysis-based Graph Program Extraction algorithm](GraphProgramExtraction.md) would not work well for Python given its highly dynamic nature.  This led us down the path of having to pick another language to work with, and we wanted to approach this methodically.  As such, we defined goals for the project, explored which properties of a programming language are important to achieve those goals, and then evaluated a lot of languages against these properties.  You already know the outcome--we eventually settled on Swift.
+As discussed in the [design overview document](DesignOverview.md) our project goal is to improve usability of TensorFlow.  We quickly realized that our core [static analysis-based Graph Program Extraction algorithm](GraphProgramExtraction.md) would not work well for Python given its highly dynamic nature.  This led us down the path of having to pick another language to work with, and we wanted to approach this methodically.  As such, we defined goals for the project, explored which properties of a programming language are important to achieve those goals, and then evaluated a lot of languages against these properties.  You already know the outcome--we eventually settled on Swift.
 
 Below we explain [our project goals](#project-goals), discuss the [programming language properties](#properties-of-programming-languages) that contribute to these goals, provide a short [evaluation of specific languages](#which-languages-fit-our-project-requirements) against those goals, and discuss the [pros and cons of Swift](#evaluating-swift-against-our-language-properties) specifically.