Skip to content
This repository was archived by the owner on Nov 5, 2024. It is now read-only.

Commit 75f475c

Browse files
Update con_overview_of_environments.adoc
1 parent 66eb8ba commit 75f475c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/modules/ROOT/pages/how-to-guides/managing-environments/con_overview_of_environments.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The following sections further explain these different environments and how you
99

1010
== Static environments
1111

12-
By default, {ProductName} deploys your application to AWS through Red Hat OpenShift Service on AWS (ROSA). This default static environment runs your application for as long as you wish. But you can host your application in a different static environment, using a bring your own cluster (BYOC) option.
12+
By default, {ProductName} deploys your application to AWS through Red Hat OpenShift Service on AWS (ROSA). This default static environment runs your application for as long as you want. But you can host your application in a different static environment, using a bring your own cluster (BYOC) option.
1313

1414
Currently, with the BYOC option, you can use a static environment hosted by any of the major cloud providers — AWS, Azure, GCP, etc.
1515

@@ -19,7 +19,7 @@ You might want to deploy your application as part of a custom integration test.
1919

2020
Normally, {ProductName} runs integration tests in the static development environment. But to deploy your application during a test, you need a new environment. The static development environment might already host the latest version of your application.
2121

22-
This is where temporary environments come in. You can configure {ProductName} to deploy your application to a temporary clone of the development environment. You can perform this configuration when adding an integration test. {ProductName} then clones the environment each time it performs the test. The temporary environment disappears after testing.
22+
This is the use case for temporary environments. You can configure {ProductName} to deploy your application to a temporary clone of the development environment. You can perform this configuration when adding an integration test. {ProductName} then clones the environment each time it performs the test. The temporary environment disappears after testing.
2323

2424
== Additional resources
2525

0 commit comments

Comments
 (0)