Resolved PR comments

Author: catmo-syntasso

docs/main/02-intro.md

@@ -48,7 +48,7 @@ With Promises, domain specialists can guarantee that every service request adher
 ### Application Developers 
 Many application teams face delays waiting for essential platform services, leading to poor developer experience (DevEx), workarounds, shadow IT, and missed deadlines. The additional concerns—such as infrastructure, networking, security policies, and billing limits—can overwhelm teams, diverting focus from delivering value.
 
-Effective platforms minimize cognitive load by offering everything-as-a-service with built-in business rules and policies. Kratix and Promises enable this while allowing Platform teams to provide services at the right level of abstraction—hiding complexity from those who don’t need to manage it.
+Effective platforms minimise cognitive load by offering everything-as-a-service with built-in business rules and policies. Kratix and Promises enable this while allowing Platform teams to provide services at the right level of abstraction—hiding complexity from those who don’t need to manage it.
 
 ## Kratix in action
 Watch how Kratix supports teams using Backstage to provide anything-as-a-service.

docs/main/03-reference/11-promises/01-intro.md

@@ -6,7 +6,7 @@ description: Documentation for the Kratix Promise Custom Resource
 
 # Promises
 
-At the core of Kratix are Promises. Promises are a set of instructions written in YAML that will produce a [resource](../resources/intro) whenever the Promise is invoked. This means that you can run software-as-a-service from your platform. A Promise consists of an API description of how to provision the dependencies required to fulfill that promise, the workflows that define how the provisioning takes place, and destination rules that allow the Promise Author to determine where resources should go.
+At the core of Kratix are Promises. Promises are a set of instructions written in YAML that will produce a [resource](../resources/intro) whenever the Promise is invoked. This means that you can run software-as-a-service from your platform. A Promise consists of the dependencies it must setup before the Promise can be requested, an API description of how a user can request that Promise, the workflows that define how the provisioning takes place, and destination rules that allow the Promise Author to determine where resources should go.
 
 This introduction is intended for platform engineers and people creating promises for use by the rest of their organisation.
 
@@ -140,7 +140,7 @@ For example, if the Promise describes a database, a Jenkins installation, and an
 Dependencies are everything that the Promise relies on to function. A Kratix Promise can even be built on other Kratix Promises. A dependency is the pre-requisite software to create the resource and make it operational. A dependency might be a low-level resource such as a database, a pre-defined environment, a connection, a queue, or a bundle of related items that work together.
 
 ### Workflows
-Workflows are the actions that must run in order to fulfill a Promise. They are a chain of containers that execute in sequence to fulfill the promise specifications, including responses to API specifications, notifications, business rules, and custom specifications.
+Workflows are the actions that must run in order to fulfil a Promise. They are a chain of containers that execute in sequence to fulfill the promise specifications, including responses to API specifications, notifications, business rules, and custom specifications.
 
 The Promise workflows are run as part of the Promise lifecycle, and the Resource workflows are run as part of the Resource lifecycle. Under both Promise and Resource workflows, Kratix supports two workflow types:
 - The `configure` workflows runs when either the Promise or Resource is created, updated or reconciled.

docs/main/03-reference/11-promises/02-create.md

@@ -5,7 +5,7 @@ description: Documentation on creating a Promise
 ---
 
 ## Getting Started
-When you start using Kratix, many people install a Marketplace Promise to experiment with. As you use it, it may become clear that you need a more customised solution.
+When getting started with Kratix, many people install a Marketplace Promise to experiment with. As you use it, it may become clear that you need a more customised solution.
 
 You clone the Promise and tweak the Promise description to apply to your own environment. You then install it so the Promise is available for request.
 
@@ -16,9 +16,9 @@ We suggest these examples as good starting places:
 - [Promise writing guide](../../../workshop/part-ii/writing-your-first-promise)
 
 ## Creating a Promise
-You create a Promise by assembling a YAML file which defines all the dependencies and workflows that the Promise will include. It also defines the API that is used to request a resource. The Promise can have a mix of static and configurable resources, or other Kratix Promises. Once the Promise is written, it needs to be installed so that the resources it refers to will be available when a user requests them.
+You create a Promise by assembling a YAML file which defines all the dependencies and workflows that the Promise will include. It also defines the API that is used to request a resource. Once the Promise is written, it needs to be installed so that the dependencies it refers to will be available when a user requests them.
 
-This example of a Promise contains all the essential elements. For Promises that have more complexity, you can see the Promise Marketplace. 
+Below is an example of a Promise contains all the essential elements. For Promises that have more complexity, you can see the Promise Marketplace. 
 
 First, there is the metadata that describes the Promise name, version, and labels. 
 
@@ -45,7 +45,7 @@ Dependencies are all the things required for the platform to run the Promise. Fo
         name: promise-example
 ```
 
-The API is how the user creates and customises their resources. The API can create, update, or delete promise instances. Users can also use the API to customise the Promise request in ways made available by the Promise. For example, the container image of a resource or its size. 
+The API is how the user creates and customises their resources. Using the API, application teams can create, update, or delete promise instances. Users can also use the API to customise the Promise request in ways made available by the Promise. For example, the container image of a resource or its size. 
 
 ```
  api:
@@ -77,7 +77,7 @@ The API is how the user creates and customises their resources. The API can crea
           storage: true
 ```
 
-Workflows are a set series of containers executed in sequence. Putting the actions in containers allows them to be consistent and reusable. Containerising the actions allows for maximum flexibility in language and modularity while maximising testability.
+Workflows are a series of containers executed in sequence. Putting the actions in containers allows them to be consistent and reusable. Containerising the actions allows for maximum flexibility in language and modularity while maximising testability.
 
 ```
   workflows:
@@ -109,4 +109,4 @@ Workflows are a set series of containers executed in sequence. Putting the actio
 
 ## Installing a Promise
 
-Installing a Promise is a simple application of the Promise YAML file to the platform cluster. The API is then available for users to call, promise-workflows execute, and the dependencies are installed and made available so that the Promise can be fulfilled when it is requested. A promise exists on the platform cluster and can be called to create an identical promise instance at any time.
+Installing a Promise is a simple application of the Promise YAML file to the platform cluster. The API is then available for users to call, promise-workflows execute, and the dependencies are installed and made available so that the Promise can be fulfilled when it is requested. A promise exists on the platform cluster and can be called to create an consistent promise instance at any time.

docs/main/03-reference/11-promises/04-delete.md

@@ -5,12 +5,6 @@ sidebar_label: Deleting
 ---
 Deleting a Promise deletes both the Promise and all the resources and dependencies associated with it. Deleting a Promise runs the specific delete workflow that is declared in the Promise. Once the delete workflow runs, the resources uniquely associated with that Promise are removed from the platform and finally the Promise itself is removed from the platform.
 
-:::caution
-
-Deleting a Promise will cascade delete all the associated requested Resources and Dependencies.
-
-:::
-
 To delete a Promise, run the command below, making sure to replace the
 `<promise name>` with the Promise you want to remove: