fix grammar an -> a

Author: jmcook1186

website/docs/01-overview.md

@@ -16,7 +16,7 @@ Modern applications are composed of many smaller pieces of software (components)
 
 The impacts of software components also vary over time, so as well as understanding **which** components contribute most to the overall impacts, there is also a question of **when** they contribute the most.
 
-Only through a granular analysis of the impacts of your software system can investments in reducing its impact be prioritized and verified. Measurement is the first and most crucial step in greening a software system, and the first step in that process with the [Impact Framework](./04-specification/impact-framework.md) is to create an [Graph](./04-specification/impact-graph.md).
+Only through a granular analysis of the impacts of your software system can investments in reducing its impact be prioritized and verified. Measurement is the first and most crucial step in greening a software system, and the first step in that process with the [Impact Framework](./04-specification/impact-framework.md) is to create a [Graph](./04-specification/impact-graph.md).
 
 ## Navigating these docs
 

website/docs/03-Terminology.md

@@ -38,7 +38,7 @@ A [Graph](specification/graph.md) is made up of nodes, each node represents eith
 ### Component
 
 **aka**: *component node*
-A component is something that creates environmental impacts, for example a server, network traffic. If it creates and environmental impact it's called a component. They effectively form the leaf nodes of an [Graph](specification/graph.md). Each component has at least one [Model Plugin](specification/model-plugin.md) configured as well as some [Inputs](inputs.md). We pass the observations to the model plugin which interacts with a model to calculate the [Impact](Impact) for this component.
+A component is something that creates environmental impacts, for example a server, network traffic. If it creates and environmental impact it's called a component. They effectively form the leaf nodes of a [Graph](specification/graph.md). Each component has at least one [Model Plugin](specification/model-plugin.md) configured as well as some [Inputs](inputs.md). We pass the observations to the model plugin which interacts with a model to calculate the [Impact](Impact) for this component.
 
 ### Grouping
 

website/docs/04-specification/impl.md

@@ -1,15 +1,15 @@
 ---
 author: Asim Hussain (@jawache)
-abstract: Describes the structure and purpose of Impact YAML, a file format to represent an Impact Graph.
+abstract: Describes the structure and purpose of Impact YAML, a file format to represent a Graph.
 ---
 # Impl (Impact YAML)
 
-- Impact YAML (IMPL) is a file format based on [yaml](https://circleci.com/blog/what-is-yaml-a-beginner-s-guide/)  to represent an [Impact Graph](graph.md). 
-- Just like an Impact Graph, an IMPL is a calculation manifest containing everything you want to measure and how you want to measure it. 
+- Impact YAML (IMPL) is a file format based on [yaml](https://circleci.com/blog/what-is-yaml-a-beginner-s-guide/)  to represent a [Graph](graph.md). 
+- Just like a Graph, an IMPL is a calculation manifest containing everything you want to measure and how you want to measure it. 
 - IMPL being YAML means it's more human-readable and can be used as a **formal method of writing use cases**, such as SCI use cases.
 - IMPL files can be named `.yaml` (or `.impl`).
 - IMPLs can be computed on the command line using the [Impact](Impact.md) tool, printing out the results to file or STDOUT.
-- You can do much more using the [Impact Graph](graph.md) SDK directly; however, for many use cases, IMPL works fine.
+- You can do much more using the [Graph](graph.md) SDK directly; however, for many use cases, IMPL works fine.
 
 ## Use Cases
 
@@ -29,8 +29,8 @@ The command line tool [Impact](Impact.md) can compute an IMPL file and generate
 
 ### To bootstrap code
 
-- IMPLs will be able to represent simple calculation manifest but to handle larger, more complex systems, we will have to write Impact Graphs as code using our SDK.
-- To help bootstrap the process, humans can write the high-level structure using IMPL and run through a tool to generate starter Impact Graph code in any language our SDK supports.
+- IMPLs will be able to represent simple calculation manifest but to handle larger, more complex systems, we will have to write Graphs as code using our SDK.
+- To help bootstrap the process, humans can write the high-level structure using IMPL and run through a tool to generate starter Graph code in any language our SDK supports.
 
 ## Structure
 

website/docs/04-specification/inputs.md

@@ -1,11 +1,11 @@
 ---
 author: Asim Hussain (@jawache)
-abstract: Describes an input in the context of an Impact Graph.
+abstract: Describes an input in the context of a Graph.
 ---
 
 # Inputs
 
-`inputs` are a core component of an [Impact Graph](graph.md) (graph), and they form the primary input into an [Impact Model Plugin](Impact%20Model%20Plugin.md) (model).
+`inputs` are a core component of a [Graph](graph.md) (graph), and they form the primary input into an [Impact Model Plugin](Impact%20Model%20Plugin.md) (model).
 
 An **input** is something you measure regarding a component in your software system. For example, an `input` about a server might be CPU utilization. `inputs` are passed into models which generate impact metrics.
 
@@ -75,7 +75,7 @@ As discussed in the [Granularity](Granularity.md) design document, an essential
 
 One dimension of granularity is time, and `inputs` are how we provide that temporal granularity.
 
-You can provide one single `input` for a long duration for every component in an [Impact Graph](graph.md); however, this won't give you a view of how the impacts changed over time. 
+You can provide one single `input` for a long duration for every component in a [Graph](graph.md); however, this won't give you a view of how the impacts changed over time. 
 
 This is why `inputs` are a time series; the more inputs you can provide about components over time, the more the Impact Framework can surface impacts over time.
 

website/docs/04-specification/model-plugin.md

@@ -4,7 +4,7 @@ abstract: Standardising the interface to measurement models.
 ---
 # Model Plugin
 
-Calculating outputs for every component in an [Impact Graph](graph.md) (graph) requires the use of an **Impact Model** (model) called through an [Impact Model Plugin](Impact%20Model%20Plugin.md) (model plugin).
+Calculating outputs for every component in a [Graph](graph.md) (graph) requires the use of an **Impact Model** (model) called through an [Impact Model Plugin](Impact%20Model%20Plugin.md) (model plugin).
 
 ## What are Impact Models?