[hotfix] Fill in links to 3.0.0 docs
diff --git a/deployments/aws-lambda/README.md b/deployments/aws-lambda/README.md
index 4c18461..6036edf 100644
--- a/deployments/aws-lambda/README.md
+++ b/deployments/aws-lambda/README.md
@@ -38,9 +38,9 @@
### Configure StateFun Module Specification
-The AWS Lambda endpoint URL should be configured as a function endpoint in your [Module Specification]().
+The AWS Lambda endpoint URL should be configured as a function endpoint in your [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/).
-Note how you may use [templating]() in the endpoint URL for multiple functions under the same namespace.
-This allows you to add new AWS Lambda functions, potentially individually serving different StateFun functions, under
-separate paths of the same AWS API Gateway endpoint. This provides flexibility to upgrade your StateFun application
-by dynamically adding new functions without having to restart the StateFun runtime.
+Note how you may use [templating](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/#url-template)
+in the endpoint URL for multiple functions under the same namespace This allows you to add new AWS Lambda functions,
+potentially individually serving different StateFun functions, under separate paths of the same AWS API Gateway endpoint.
+This provides flexibility to upgrade your StateFun application by dynamically adding new functions without having to restart the StateFun runtime.
diff --git a/java/greeter/README.md b/java/greeter/README.md
index bf2c37d..2e739b5 100644
--- a/java/greeter/README.md
+++ b/java/greeter/README.md
@@ -22,9 +22,9 @@
our functions service, hosting the `UserFn` and `UserLogin` behind a HTTP endpoint. Check out the source code under
`src/main/java`. The `Dockerfile` is used to build a Docker image for our functions service.
- `user-logins.txt`: A file with multiple JSON objects per line; this is used as test events produced to our application ingress.
-- `module.yaml`: The [Module Specification]() file to be mounted to the StateFun runtime process containers. This
+- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
configures a few things for a StateFun application, such as the service endpoints of the application's functions, as
- well as definitions of [Ingresses and Egresses]() which the application will use.
+ well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/io-module/overview/) which the application will use.
- `docker-compose.yml`: Docker Compose file to spin up everything.
## Prerequisites
diff --git a/java/shopping-cart/README.md b/java/shopping-cart/README.md
index c773dbf..75233ad 100644
--- a/java/shopping-cart/README.md
+++ b/java/shopping-cart/README.md
@@ -9,9 +9,9 @@
- `src/`, `pom.xml` and `Dockerfile`: These files and directories are the contents of a Java Maven project which builds
our functions service, hosting the `UserShoppingCartFn` and `StockFn` behind a HTTP endpoint. Check out the source code under
`src/main/java`. The `Dockerfile` is used to build a Docker image for our functions service.
-- `module.yaml`: The [Module Specification]() file to be mounted to the StateFun runtime process containers. This
+- `module.yaml`: The [Module Specification](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/deployment/module/) file to be mounted to the StateFun runtime process containers. This
configures a few things for a StateFun application, such as the service endpoints of the application's functions, as
- well as definitions of [Ingresses and Egresses]() which the application will use.
+ well as definitions of [Ingresses and Egresses](https://ci.apache.org/projects/flink/flink-statefun-docs-release-3.0/docs/io-module/overview/) which the application will use.
- `docker-compose.yml`: Docker Compose file to spin up everything.
- `playthrough`: utilities for automatically playing through the interactions scenarios.
