Merge pull request #61910 from openshift-cherrypick-robot/cherry-pick…

…-61308-to-enterprise-4.14

[enterprise-4.14] RHDEVDOCS-5391: Add Operator prerequisites to JAR upload docs

modules/odc-deploying-java-applications.adoc

@@ -1,41 +1,47 @@
+// Module included in the following assemblies:
+//
+// * applications/creating_applications/odc-creating-applications-using-developer-perspective.adoc
+
 :_content-type: PROCEDURE
 [id="odc-deploying-java-applications_{context}"]
-= Upload JAR files for easy deployment of Java applications
+= Deploying a Java application by uploading a JAR file
 
-You can use the JAR files in the *Topology* view of the *Developer* perspective to deploy your Java applications. You can upload a JAR file using the following options:
+You can use the web console *Developer* perspective to upload a JAR file by using the following options:
 
-* Navigate to the *+Add* view of the *Developer* perspective, and click *Upload JAR file* in the *From Local Machine* tile. Browse and select your JAR file, or drag and drop a JAR file to deploy your application.
+* Navigate to the *+Add* view of the *Developer* perspective, and click *Upload JAR file* in the *From Local Machine* tile. Browse and select your JAR file, or drag a JAR file to deploy your application.
 
-* Navigate to the *Topology* view and use the *Upload JAR file* option, or drag and drop a JAR file to deploy your application.
+* Navigate to the *Topology* view and use the *Upload JAR file* option, or drag a JAR file to deploy your application.
 
 * Use the in-context menu in the *Topology* view, and then use the *Upload JAR file* option to upload your JAR file to deploy your application.
 
-Use the following instructions to upload a JAR file in the *Topology* view to deploy a Java application:
+.Prerequisites
+
+* The Cluster Samples Operator must be installed by a cluster administrator.
+* You have access to the {product-title} web console and are in the *Developer* perspective.
 
 .Procedure
 
-. In the *Topology* view, right-click anywhere in the *Topology* view to see the *Add to Project* menu.
+. In the *Topology* view, right-click anywhere to view the *Add to Project* menu.
 
-. Hover over the *Add to Project* menu to see the menu options, and then select the *Upload JAR file* option to see the *Upload JAR file* form . Alternatively, you can drag and drop the JAR file in the *Topology* view.
+. Hover over the *Add to Project* menu to see the menu options, and then select the *Upload JAR file* option to see the *Upload JAR file* form. Alternatively, you can drag the JAR file into the *Topology* view.
 
-. In the *JAR file* field, browse for the required JAR file on your local machine and upload it. Alternatively, you can drag and drop the JAR file on the field. A toast alert is displayed at the top right if an incompatible file type is dragged and dropped on the *Topology* view. A field error is displayed if an incompatible file type is dropped on the field in the upload form.
+. In the *JAR file* field, browse for the required JAR file on your local machine and upload it. Alternatively, you can drag the JAR file on to the field. A toast alert is displayed at the top right if an incompatible file type is dragged into the *Topology* view. A field error is displayed if an incompatible file type is dropped on the field in the upload form.
 
-. You can further specify optional Java commands to customize your deployed application. The Runtime Icon and Builder Image is selected by default. If a Builder Image is not auto-detected, select a Builder Image. If required, you can change the version using the *Builder Image Version* drop-down list.
+. The runtime icon and builder image are selected by default. If a builder image is not auto-detected, select a builder image. If required, you can change the version using the *Builder Image Version* drop-down list.
 
-. In the optional *Application Name* field, enter a unique name for your application for the resource labelling.
+. Optional: In the *Application Name* field, enter a unique name for your application to use for resource labelling.
 
 . In the *Name* field, enter a unique component name for the associated resources.
 
-. Optional: Using the *Resource type* drop-down list, select a different resource type from the list of default resource types. 
+. Optional: Use the *Resource type* drop-down list to change the resource type. 
 
-. In the *Advanced options*, click *Create a Route to the Application* to configure a public URL for your deployed application.
+. In the *Advanced options* menu, click *Create a Route to the Application* to configure a public URL for your deployed application.
 
-. Click *Create* to deploy the application. The user sees a toast notification notifying that the JAR file is being uploaded and takes a while. The toast notification also includes a link to view the build logs.
+. Click *Create* to deploy the application. A toast notification is shown to notify you that the JAR file is being uploaded. The toast notification also includes a link to view the build logs.
 
-+
 [NOTE]
 ====
-If the user attempts to close the browser tab while the build is running, a web alert would be displayed asking the user if they actually want to leave the page.
+If you attempt to close the browser tab while the build is running, a web alert is displayed.
 ====
 
-After the JAR file is uploaded and the application is deployed, you can see the deployment in the *Topology* view.
+After the JAR file is uploaded and the application is deployed, you can view the application in the *Topology* view.