/docs -> docs.

docs/deployment-operations/errors.md

@@ -72,7 +72,7 @@ Make sure, when updating a service endpoint, to assign it a new uri.
 
 You can force the override using the `"force": true` field in the discover request, but beware that this can lead in-flight invocations to an unrecoverable error state.  
 
-See the [versioning documentation](http://restate.dev/docs/deployment-operations/versioning) for more information.
+See the [versioning documentation](./versioning) for more information.
 
 ## META0005 {#META0005}
 
@@ -89,7 +89,7 @@ When implementing a new service revision, make sure that:
 * The service instance type and the key definition, if any, is exactly the same as of the previous revisions.
 * The Protobuf contract and message definitions are backward compatible.
 
-See the [versioning documentation](http://restate.dev/docs/deployment-operations/versioning) for more information.
+See the [versioning documentation](./versioning) for more information.
 
 ## RT0001 {#RT0001}
 
@@ -105,7 +105,7 @@ Suggestions:
 
 Cannot start Restate because the configuration cannot be parsed. Check the configuration file and the environment variables provided.
 
-For a complete list of configuration options, and a sample configuration, check http://restate.dev/docs/deployment-operations/configuration
+For a complete list of configuration options, and a sample configuration, check http://docs.restate.dev/deployment-operations/configuration
 
 ## RT0003 {#RT0003}