From 5f0bb1dfb51c600425b6de9e66ceaaadf707bfd4 Mon Sep 17 00:00:00 2001
From: Adam Harvey <adam.harvey@dxc.com>
Date: Wed, 23 Dec 2020 14:27:48 -0500
Subject: [PATCH] Fix typo and rewording

---
 .../ProjectGrowthInstructionsPage.tsx                       | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/plugins/cost-insights/src/components/ProjectGrowthInstructionsPage/ProjectGrowthInstructionsPage.tsx b/plugins/cost-insights/src/components/ProjectGrowthInstructionsPage/ProjectGrowthInstructionsPage.tsx
index 4fcc34c87f..dcd33a02e8 100644
--- a/plugins/cost-insights/src/components/ProjectGrowthInstructionsPage/ProjectGrowthInstructionsPage.tsx
+++ b/plugins/cost-insights/src/components/ProjectGrowthInstructionsPage/ProjectGrowthInstructionsPage.tsx
@@ -101,7 +101,7 @@ export const ProjectGrowthInstructionsPage = () => {
       <Typography variant="h1">Investigating cloud cost growth</Typography>
       <Typography paragraph>
         Cost Insights shows an alert when costs for a particular billing entity,
-        such as a GCP project, have grown at a rate faster than our alerting
+        such as a GCP project, has grown at a rate faster than our alerting
         threshold. The responsible team should follow this guide to decide
         whether this warrants further investigation.
       </Typography>
@@ -135,7 +135,7 @@ export const ProjectGrowthInstructionsPage = () => {
         <Typography paragraph>
           Next, evaluate whether the growth is significant. This helps avoid
           premature optimization, where cost in engineering time is more than
-          would be saved from the optimization over a reasonable timeframe.
+          would be saved from the optimization over a reasonable time frame.
         </Typography>
         <Typography paragraph>
           We recommend reframing the cost growth itself in terms of engineering
@@ -205,7 +205,7 @@ export const ProjectGrowthInstructionsPage = () => {
           Is the workload using cloud resources efficiently? For compute
           resources, do the utilization metrics look reasonable? Autoscaling
           infrastructure, such as Kubernetes, can run workloads more efficiently
-          without comprimising reliability.
+          without compromising reliability.
         </Typography>
         <Typography variant="h5">Lifecycle</Typography>
         <Typography paragraph>