reacheable -> reachable (#120)

restatedev · Aug 19, 2023 · 1b242bd · 1b242bd
1 parent 1c4cd21
commit 1b242bd
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/services/deployment/general.md b/docs/services/deployment/general.md
@@ -11,9 +11,9 @@ A service endpoint can be deployed as a Lambda function, a Kubernetes pod, a Kna
 
 The URL (including path prefix) MUST be **unique**, meaning that no two service endpoints with the same URL can exist at the same time in a Restate instance.
 
-Moreover, service endpoints are **immutable**, and are assumed to be reacheable throughout the entire lifecycle of an invocation. To deploy any change to a service, either in the Protobuf definition or in the business logic, you should deploy a new service endpoint with a new URL. See the [versioning documentation](/services/upgrades-removal) for more details on how to update services.
+Moreover, service endpoints are **immutable**, and are assumed to be reachable throughout the entire lifecycle of an invocation. To deploy any change to a service, either in the Protobuf definition or in the business logic, you should deploy a new service endpoint with a new URL. See the [versioning documentation](/services/upgrades-removal) for more details on how to update services.
 
 
 :::info Running services locally
 Have a look at the [Quickstart](/quickstart) to set up your local development environment.
-:::
+:::
diff --git a/docs/services/upgrades-removal.md b/docs/services/upgrades-removal.md
@@ -9,7 +9,7 @@ Restate comes with different solutions to update the services, to simplify devel
 
 ## Deploy a new service revision
 
-As described in the [deployment documentation](/services/deployment/general), *service endpoints* are immutable, and are assumed to be reacheable throughout the entire lifecycle of an invocation. In order to deploy any change to a service, either in the protobuf definition and/or in the business logic, a new service endpoint should be deployed and registered.
+As described in the [deployment documentation](/services/deployment/general), *service endpoints* are immutable, and are assumed to be reachable throughout the entire lifecycle of an invocation. In order to deploy any change to a service, either in the protobuf definition and/or in the business logic, a new service endpoint should be deployed and registered.
 
 When registering a new service endpoint, Restate will detect if it contains already registered services, and will treat them as new revisions. Any new invocations to that service will be executed by the newly registered service endpoint, thus guaranteeing that new invocations are always routed to the latest service revision, while *old* invocations will continue to use the previous service endpoint. It must be guaranteed that the old service endpoint lives until all the existing invocations complete.