Merge pull request #129 from Green-Software-Foundation/rename-manifest-imp-2

more renaming

Author: jmcook1186

docs/major-concepts/imp-file.md

@@ -2,9 +2,9 @@
 sidebar-position: 2
 ---
 
-# Manifest File
+# IMP Files
 
-Manifest files are fundamental to Impact Framework and they serve multiple important purposes, including:
+IMP files are fundamental to Impact Framework and they serve multiple important purposes, including:
 
 - They contain all the necessary configurations for Impact Framework
 - They define your application architecture
@@ -25,7 +25,7 @@ Anyone can download Impact Framework and execute an IMP file to verify the resul
 
 ### Overview
 
-Manifest files can be simple or very intricate, depending on the plugin pipeline you want to use and the complexity of your application. However, all IMP files conform to a basic structure that looks as follows:
+IMP files can be simple or very intricate, depending on the plugin pipeline you want to use and the complexity of your application. However, all IMP files conform to a basic structure that looks as follows:
 
 ```yaml
 name:

docs/pipelines/cpu-to-carbon.md

@@ -165,7 +165,7 @@ correct-cpu-energy-for-vcpu-ratio:
   output: cpu/energy
 ```
 
-## Manifest
+## IMP
 
 ```yaml
 name: teads curve demo

docs/pipelines/instance-metadata.md

@@ -84,7 +84,7 @@ extract-processor-name:
     output: cpu/name
 ```
 
-## Manifest
+## IMP
 
 ```yaml
 name: instance-metadata

docs/pipelines/sci.md

@@ -189,7 +189,7 @@ sci:
   functional-unit: users
 ```
 
-## Manifest
+## IMP
 
 ```yaml
 name: sci example

docs/pipelines/template.txt

@@ -30,7 +30,7 @@
 
 <!--- List the plugins used, the instance names, a brief description of the purpose of each instance and list out the config for each instance. -->
 
-## Manifest
+## IMP
 
 <!--- Provide the IMP in full. -->
 

docs/users/how-to-use-the-explain-feature.md

@@ -4,7 +4,7 @@ sidebar_position: 7
 
 # How to check parameters and units using `explainer`
 
-Manifest files can get complicated, especially when there are many plugin instances initialized. It can be challenging to keep track of the flow of parameters and their units through a pipeline. To help IMP authors and auditors verify the correct flow of information through a pipeline, we provide the `explainer` feature.
+IMP files can get complicated, especially when there are many plugin instances initialized. It can be challenging to keep track of the flow of parameters and their units through a pipeline. To help IMP authors and auditors verify the correct flow of information through a pipeline, we provide the `explainer` feature.
 
 `explainer` adds a block to the IMP that simply lists the parameter metadata used be the plugin's instance in the IMP. The metadata contains: