zuplo 7.4.1 → 7.4.3

package/docs/programmable-api/environment.mdx

@@ -4,7 +4,7 @@ sidebar_label: Environment Variables
 ---
 
 The `environment` object provides access to environment variables in your Zuplo
-API gateway. It returns a record of environment variable names to their values.
+Gateway. It returns a record of environment variable names to their values.
 
 :::info{title="Configuration Guide"}
 

package/docs/programmable-api/jwt-service-plugin.mdx

@@ -30,7 +30,7 @@ Some of the common use cases for the JWT service plugin include:
 
 - Securing downstream APIs by issuing JWTs that can be used to verify that the
   request is coming from your Zuplo API
-- Securing requests to other Zuplo API gateways (for example, when using the
+- Securing requests to other Zuplo Gateways (for example, when using the
   [Federated Gateway](../dedicated/federated-gateways.mdx) capability on Zuplo
   managed dedicated deployments.)
 - Calling third-party APIs that can be configured with federated identity such

package/docs/programmable-api/logger.mdx

@@ -3,7 +3,7 @@ title: Logger
 ---
 
 The `Logger` interface provides structured logging capabilities throughout your
-Zuplo API gateway. The logger is accessible via the `context.log` property and
+Zuplo Gateway. The logger is accessible via the `context.log` property and
 supports multiple log levels.
 
 ## Interface

package/docs/programmable-api/runtime-errors.mdx

@@ -3,7 +3,7 @@ title: Runtime Errors
 ---
 
 Zuplo provides specialized error classes for handling runtime and configuration
-errors in your API gateway.
+errors in your Zuplo Gateway.
 
 ## RuntimeError
 

package/docs/programmable-api/zuplo-context.mdx

@@ -266,9 +266,9 @@ export default async function (request: ZuploRequest, context: ZuploContext) {
 
 ### `invokeRoute`
 
-Invokes another route within the same API gateway. This enables internal routing
-and composition of multiple routes. The invoked route runs with a new context
-that has `parentContext` set to the current context.
+Invokes another route within the same Zuplo Gateway. This enables internal
+routing and composition of multiple routes. The invoked route runs with a new
+context that has `parentContext` set to the current context.
 
 ```ts
 export default async function (request: ZuploRequest, context: ZuploContext) {

package/docs/self-hosted/overview.md

@@ -4,9 +4,9 @@ sidebar_label: Overview
 ---
 
 Zuplo Self-Hosted (also known as on-prem) is a deployment model where you run
-the Zuplo API Gateway on your own infrastructure — any cloud or private data
-center. Zuplo Self-Hosted runs exclusively on Kubernetes and is installed with a
-single Helm chart into your cluster.
+the Zuplo Gateway on your own infrastructure — any cloud or private data center.
+Zuplo Self-Hosted runs exclusively on Kubernetes and is installed with a single
+Helm chart into your cluster.
 
 Self-hosted deployment might be the right choice for you if you need:
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "zuplo",
-  "version": "7.4.1",
+  "version": "7.4.3",
   "type": "module",
   "description": "The programmable API Gateway",
   "author": "Zuplo, Inc.",
@@ -19,9 +19,9 @@
     "zuplo": "zuplo.js"
   },
   "dependencies": {
-    "@zuplo/cli": "7.4.1",
-    "@zuplo/core": "7.4.1",
-    "@zuplo/runtime": "7.4.1",
-    "@zuplo/test": "7.4.1"
+    "@zuplo/cli": "7.4.3",
+    "@zuplo/core": "7.4.3",
+    "@zuplo/runtime": "7.4.3",
+    "@zuplo/test": "7.4.3"
   }
 }