Improve end-to-end deployment description

docs/source/applications_packaging.rst

@@ -931,22 +931,25 @@ Deployment
     :ref:`deployment parameters <manifest-deploymentParameters>`,
     :ref:`inputs <inputs>` and :ref:`volumes <manifest-volumes>`.
 
-#.  The ``deploy.sh`` script for the selected cloud provider is executed. Near
-    real-time logs are sent via the API to the web interface for the user to
-    monitor the deployment.
+#.  The ``deploy.sh`` script for the selected cloud provider is executed. The
+    web interface queries the API for near real-time logs to let the user monitor
+    the deployment.
 
-#.  The backend monitors the ``deploy.sh`` script execution and if it fails
-    (returns a non-zero exit code), the backend flags the deployment as
-    ``DEPLOYMENT_FAILED`` and stops. The information is sent to the web application
-    and the user is offered the choice to destroy the deployment.
+#.  The deployment environment monitors the ``deploy.sh`` script execution and
+    if it fails (returns a non-zero exit code), updates the backend marking the
+    deployment as ``DEPLOYMENT_FAILED`` and stops. The web interface regularly
+    polls for updates and, once it detects the failure, offers the user the
+    choice to destroy the deployment.
 
 #.  If the ``deploy.sh`` script completes successfully, the backend executes
     the ``state.sh`` script to capture a snapshot of the provisioned infrastructure
     and looks for the defined :ref:`outputs <manifest-outputs>` in the log files.
     If the ``state.sh`` script fails (returns with a non-zero exit code) the
-    backend updates the status of the deployment to ``RUNNING_FAILED`` and the
-    user is offered the choice to destroy the deployment. Otherwise, the
-    deployment is marked as ``RUNNING`` and outputs displayed in the web interface.
+    deployment environment marks the deployment ``RUNNING_FAILED`` and the user
+    is offered the choice to destroy the deployment. Otherwise, the deployment
+    is marked as ``RUNNING`` and the web interface will be able to pull the outputs
+    from the REST API.
+
 
 #. Done!