diff --git a/qdrant-landing/content/documentation/tutorials/async-api.md b/qdrant-landing/content/documentation/tutorials/async-api.md
index d654e088e..9f1d1df60 100644
--- a/qdrant-landing/content/documentation/tutorials/async-api.md
+++ b/qdrant-landing/content/documentation/tutorials/async-api.md
@@ -31,7 +31,7 @@ that will act as a gateway. If you want to do it locally, please make sure Qdran
 in a Docker container:
 
 ```bash
-docker run -p "6333:6333" -p "6334:6334" qdrant/qdrant:v1.4.0
+docker run -p "6333:6333" -p "6334:6334" qdrant/qdrant:v1.4.1
 ```
 
 Alternatively, you can also use a [Qdrant Cloud](https://cloud.qdrant.io/) cluster. With a Cloud cluster you will pass the API key to the
@@ -54,7 +54,7 @@ efficient and is the recommended way of using Qdrant asynchronously.
 ### gRPC API
 
 Every instance of `QdrantClient` has two properties we are going to use: `async_grpc_collections` and `async_grpc_points`. They expose
-the autogenerated clients for collections and points respectively. 
+the autogenerated clients for [collections](/documentation/concepts/collections/) and [points](/documentation/concepts/points/) respectively. 
 
 The gRPC client uses type definitions for all the interactions with the server. They are autogenerated from the source code of Qdrant
 server, and we have to import them if we want to call any of the available methods.