Skip to content

Commit 1477ed5

Browse files
authored
docs: JR-339: Updates based on PR review feedback (#543)
1 parent 5180fcd commit 1477ed5

File tree

1 file changed

+6
-6
lines changed
  • docs/api-designer/getting-started-api-designer

1 file changed

+6
-6
lines changed

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -199,7 +199,7 @@ endif::[]
199199
== Importing a schema or API design
200200

201201
[role="_abstract"]
202-
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.
202+
You can import an event schema or API definition into {product-long-api-designer} from a URL, from a file, or from a running {product-long-registry} instance.
203203

204204
.Prerequisites
205205
* You're logged in to the {product-long-api-designer} web console at {service-url-api-designer}[^].
@@ -239,7 +239,7 @@ You can test the design while working in the {product-long-api-designer} editor,
239239

240240
.Prerequisites
241241
* You're logged in to the {product-long-api-designer} web console at {service-url-api-designer}[^].
242-
* You've created or imported an {product-api-designer} design.
242+
* You've created or imported a design in {product-api-designer}.
243243
* You can access a running {product-registry} instance in your organization.
244244
Within that instance, you know the artifact ID of an artifact with the required rules configured.
245245
For more information, see {base-url}{getting-started-url-registry}[Getting started with {product-long-registry}^].
@@ -273,11 +273,11 @@ endif::[]
273273
== Exporting a schema or API design
274274

275275
[role="_abstract"]
276-
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.
276+
When you're happy with the changes to your {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.
277277

278278
.Prerequisites
279279
* You're logged in to the {product-long-api-designer} web console at {service-url-api-designer}[^].
280-
* You've created or imported an {product-api-designer} design.
280+
* You've created or imported a design in {product-api-designer}.
281281
* You can access a running {product-registry} instance in your organization.
282282
For more information, see {base-url}{getting-started-url-registry}[Getting started with {product-long-registry}^].
283283

@@ -301,8 +301,8 @@ If you don't specify a version number, {registry} sets the version to 1 for the
301301
. Click *Export*.
302302
The exported design is listed on the artifacts page of the specified {registry} instance.
303303

304-
You can manage {product-long-api-designer} design versions in {product-long-registry}.
305-
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}.
304+
You can use {product-long-registry} to manage the versions of a design from {product-long-api-designer}.
305+
You can also download a design from {product-api-designer} to a file, either for local client code generation or to import the design into {product-long-api-management}.
306306

307307
.Verification
308308
ifdef::qs[]

0 commit comments

Comments
 (0)