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

glenn-rodgers-sf · bjoson-mulesoft · web-flow · commit d24542c75966 · 2024-03-08T13:53:31.000-05:00
Co-authored-by: Beth Joson &lt;88461166+bjoson-mulesoft@users.noreply.github.com&gt;
diff --git a/modules/ROOT/pages/_partials/task-add-api-instance.adoc b/modules/ROOT/pages/_partials/task-add-api-instance.adoc
@@ -83,7 +83,7 @@ See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manag
 +
 [NOTE]
 ====
-Deploying an API proxy to a self-managed server in API Manager, does not deploy the proxy to your on-premise server. After you deploy the proxy in API Manager, deploy the proxy to your on-premise server:
+Deploying an API proxy to a self-managed server in API Manager does not deploy the proxy to your on-premise server. After you deploy the proxy in API Manager, deploy the proxy to your on-premise server:
 
 . xref:download-proxy-task.adoc[Download your new API proxy JAR file].
 . xref:mule-runtime::deploy-on-premises.adoc[Deploy the JAR file to your on-premise server].

Original file line number	Diff line number	Diff line change
`@@ -83,7 +83,7 @@ See xref:runtime-manager::servers-create.adoc[Register a server in Runtime Manag`
`83`	`83`	`+`
`84`	`84`	`[NOTE]`
`85`	`85`	`====`
`86`		`-Deploying an API proxy to a self-managed server in API Manager, does not deploy the proxy to your on-premise server. After you deploy the proxy in API Manager, deploy the proxy to your on-premise server:`
	`86`	`+Deploying an API proxy to a self-managed server in API Manager does not deploy the proxy to your on-premise server. After you deploy the proxy in API Manager, deploy the proxy to your on-premise server:`
`87`	`87`
`88`	`88`	`. xref:download-proxy-task.adoc[Download your new API proxy JAR file].`
`89`	`89`	`. xref:mule-runtime::deploy-on-premises.adoc[Deploy the JAR file to your on-premise server].`