Added info about non-k8 manifest

Author: Prabha Kylasamiyer Sundara Rajan

docs/topics/mta-cli-generate-assets.adoc

@@ -8,10 +8,10 @@
 Starting from {ProductShortName} 7.3.0, you can run the `discover` and `generate` commands in the containerless {ProductShortName} {CLIName}. The commands automatically generate the manifests needed to deploy a Cloud Foundry (CF) application in the {ocp-short}. 
 
 * `Discover` command: Generates the discovery manifest in the YAML format from the CF application manifest. The discovery manifest preserves the specifications found in the CF manifest that define the metadata, runtime, and platform configurations.
-* `Generate` command: Generates the deployment manifest for {ocp} deployments by using the discovery manifest. The deployment manifest is generated by using a templating engine such as Helm that converts the discovery manifest into a Kubernetes-native format.  
+* `Generate` command: Generates the deployment manifest for {ocp} deployments by using the discovery manifest. The deployment manifest is generated by using a templating engine such as Helm that converts the discovery manifest into a Kubernetes-native format. You can also use this command to generate non-Kubernetes manifests such as a Dockerfile or a configuration file.
 
 .Benefits of generating deployment assets by using the {ProductShortName} {CLIName}
-* Extending the {ProductShortName} {CLIName} to generate the Kubernetes and non-Kubernetes deployment manifests at once.   
+* Extending the {ProductShortName} {CLIName} to generate the Kubernetes and non-Kubernetes deployment manifests.   
 * Generating deployment manifests using familiar template engines like Helm that are widely used for Kubernetes deployments.
 * Adhering to Kubernetes best practices when preparing the deployment manifest using Helm templates.