docs: JR-339: Adds reviewer feedback (#527)

* docs: JR-339: Adds reviewer feedback

* docs: JR-339: Updates the export section based on latest implementation

* docs: JR-339: Adds peer review feedback

Author: bredamc

docs/api-designer/getting-started-api-designer/README.adoc

@@ -79,7 +79,7 @@ ifdef::context[:parent-context: {context}]
 
 // Purpose statement for the assembly
 [role="_abstract"]
-As a developer of applications and services, you can use {product-long-api-designer} to design event schemas and REST API definitions that comply with vendor-neutral and portable open specifications.
+As an API owner or developer, you can use {product-long-api-designer} to design event schemas and API definitions that comply with vendor-neutral and portable open specifications.
 {product-long-api-designer} is a managed cloud service that enables you to design schemas and API definitions without having to install, configure, run, and maintain your own {product-api-designer} clusters.
 
 For more overview information, see the https://access.redhat.com/documentation/en-us/red_hat_openshift_api-designer/1[{product-long-api-designer} user documentation^].
@@ -131,7 +131,7 @@ endif::[]
 .Creating an API design
 image::create-api-designer-design.png[Image of page to create an API design]
 +
-. Click *Create* to create the design. The design editor opens automatically.
+. Click *Create*. The new API design opens in the design editor.
 . Select the design title and click the pen icon. Change the design title to *Orders* and click the *Save changes* icon.
 . Click the *Design* tab, and optionally edit the design as follows:
 .. Provide a version number and a description.
@@ -154,7 +154,7 @@ The content of the *Source* tab automatically updates when you edit values on th
 . Optional: In the left pane of the design editor, you can add the following items:
 .. OpenAPI: Resource paths, data types, and responses
 .. AsyncAPI: Channels, data types, messages, operation traits, and message traits
-. Click *Save* to save all changes and close the design editor.
+. Click *Save*.
 
 The new design is listed on the designs page. You can use the options icon (three vertical dots) to open the design editor, download the design to a file, or delete the design.
 
@@ -176,7 +176,7 @@ endif::[]
 == Creating a schema design
 
 [role="_abstract"]
-Use the {product-long-api-designer} web console to create an Apache Avro, JSON, or Google Protocol Buffers (Protobuf) event schema.
+Use the {product-long-api-designer} web console to create an Apache Avro, JSON Schema, or Google Protocol Buffers (Protobuf) event schema.
 
 ifndef::qs[]
 .Prerequisites
@@ -194,14 +194,14 @@ endif::[]
 .Creating a schema design
 image::create-schema-design.png[Image of page to create a schema design]
 +
-. Click *Create* to create the design. The design editor opens automatically.
-. Edit the design to provide your content.
+. Click *Create*. The new schema design opens in the design editor.
+. Edit the design source to provide your content.
 +
 [.screencapture]
 .Editing a schema design
 image::api-designer-schema-editor.png[Image of schema design editor]
 +
-. Click *Save* to save all changes and close the design editor.
+. Click *Save*.
 
 The new design is listed on the designs page. You can use the options icon (three vertical dots) to open the design editor, download the design to a file, or delete the design.
 
@@ -216,22 +216,23 @@ ifndef::qs[]
 endif::[]
 
 [id="proc-importing-schema-api-design_{context}"]
-== Importing an {product-long-api-designer} schema or API design
+== Importing a schema or API design
 
 [role="_abstract"]
 You can import an event schema or API definition into {product-long-api-designer} from a URL, from a file, or from an {product-long-registry} instance.
 
 .Prerequisites
 * You're logged in to the {product-api-designer} web console at {service-url-api-designer}[^].
-* You can access a running {product-registry} instance, if you want to import from {registry}.
+* You can access a running {product-registry} instance in your organization, if you want to import from {registry}.
 
 .Procedure
 . In the {service-url-api-designer}[{product-api-designer} web console], click *Import a schema or API design*, and then click one of the following options:
-.. *Import from file*: Click *Browse* and select a file, or drag and drop a file, and then click *Import*.
-.. *Import from URL*: Enter a valid and accessible URL, and then click *Import*.
-.. *Import from {registry}*: From the instances list, select a registry instance to show a list of its artifacts. Select an artifact, and then click *Import*.
-. After you import the design, the design editor opens automatically.
-. When you have finished editing, you can save your changes locally, download the content to a file, or export the updated design to {registry}.
+.. *Import from file*: Click *Browse* and select a file, or drag and drop a file.
+.. *Import from URL*: Enter a valid and accessible URL.
+.. *Import from {registry}*: From the instances list, select a {registry} instance. Browse the list of artifacts for that instance, and select an artifact.
+. Click *Import*. The design editor opens automatically.
+
+When you finish editing, you can export the updated design to {registry} as a new artifact or as a new version of the existing artifact. You can also save your changes locally, or download the content to a file.
 
 .Verification
 ifdef::qs[]
@@ -244,20 +245,20 @@ ifndef::qs[]
 endif::[]
 
 [id="proc-exporting-schema-api-design_{context}"]
-== Exporting an {product-long-api-designer} schema or API design
+== Exporting a schema or API design
 
 [role="_abstract"]
-After you create or import an {product-long-api-designer} event schema or API definition, you can export the content to an existing {product-long-registry} instance.
+When you're happy with your changes to an {product-long-api-designer} event schema or API definition, and you want to use the design in your application, you can export the content to an existing {product-long-registry} instance.
 
 .Prerequisites
 * You're logged in to the {product-api-designer} web console at {service-url-api-designer}[^].
 * You've created or imported an {product-api-designer} design.
-* You can access a running {product-registry} instance.
+* You can access a running {product-registry} instance in your organization.
 
 .Procedure
 . In the *{product-api-designer}* designs page of the web console, select the {product-api-designer} design that you want to export.
 . Click *Edit* to open the design editor.
-. From the *Save to* menu, click *Export to {registry}*.
+. From the *Actions* menu, click *Export to {registry}*.
 . Complete the form to specify where the new design should be saved.
 +
 NOTE: If the design was originally imported from {product-registry}, the fields are prepopulated with the details of the original {product-registry} instance, and the *Version* is incremented.
@@ -269,7 +270,12 @@ NOTE:  Specifying a group is optional when using the web console: {registry} gen
 +
 .. *Artifact ID*: Enter an optional unique ID for this artifact, such as `my-ID`. If you don't specify a unique artifact ID, {registry} generates one automatically as a UUID.
 .. *Version*: Specify the version number.
-. Click *Save*.
++
+[.screencapture]
+.Exporting an API design
+image::export-api-designer-design.png[Image of page to export an API design]
++
+. Click *Export*.
 
 You can manage {product-long-api-designer} design versions in {product-long-registry}. You can also download {product-api-designer} designs to a file, either for local client code generation or to import the designs into {product-long-api-management}.