Skip to content

Commit d8cb638

Browse files
failupdmerlob
andauthored
Update modules/ROOT/pages/_partials/task-add-api-instance.adoc
Co-authored-by: Daniela Merlo <97902112+dmerlob@users.noreply.github.com>
1 parent 66e071b commit d8cb638

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

modules/ROOT/pages/_partials/task-add-api-instance.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manag
8080
.. Select a target from the list or click **Add server**.
8181
.. Enter a *Proxy app name*.
8282
83-
* *Self-managed Server:* Select this option if you want to create a JAR file to deploy an API proxy to a Mule runtime running on an on-premises server that is not registered in Runtime Manager. For more information, see xref:mule-runtime::mule-deployment-model.adoc[].
83+
* *Self-managed Server:* Select this option if you want to create a JAR file to deploy an API proxy to a Mule runtime instance running on an on-premises server that is not registered in Runtime Manager. For more information, see xref:mule-runtime::mule-deployment-model.adoc[].
8484
====
8585
Deploying an API proxy to a self-managed server in API Manager doesn’t deploy the proxy to your on-premises server. After you deploy the proxy in API Manager, deploy the proxy to your on-premises server:
8686
. xref:download-proxy-task.adoc[Download your new API proxy JAR file].

0 commit comments

Comments
 (0)