Update docs/modules/ROOT/pages/how-to-guides/managing-environments/pr…

…oc_creating_your_own_environment.adoc

Co-authored-by: Gaurav Trivedi <[email protected]>

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

@@ -53,7 +53,7 @@ users:
 If any errors occur while creating your environment, complete the following steps: 
 
 . Make sure the token you provided in your `kubeconfig` file is valid. If the token in your `kubeconfig` file has expired, log in to your cluster and request a new token.
-. Verify that you entered the correct values in the correct places in your `kubeconfig` file. When reading the example file, you can easily mistake the namespace, `rhn-support-csears-dev`, for the username, `rhn-support-csears`, and vice versa.  
+. Make sure that you entered the correct values in the right places in your `kubeconfig` file. When  you read the example file, you might easily mistake the namespace, `rhn-support-csears-dev`, for the username, `rhn-support-csears`, and vice versa.  
 . Make sure that your cluster supports another Pod for deploying your application.
 . If you do not find any errors in your `kubeconfig` file, go to *Environments* in the {ProductName} UI, select the three dots next to the environment you created, select *Delete*, and then create a new environment.
 . If that still does not work, try clearing the cache of your browser. If you are using Chrome, try deleting and creating the environment again using an Incognito window.