diff --git a/.github/vale/dicts/aiven.dic b/.github/vale/dicts/aiven.dic
index 550610ae5a..c27562a2fc 100644
--- a/.github/vale/dicts/aiven.dic
+++ b/.github/vale/dicts/aiven.dic
@@ -61,7 +61,6 @@ failover
 fileset
 filesets
 Flink
-Flink's
 Gantt
 geocoder
 geocoding
diff --git a/docs/products/flink/concepts/flink-architecture.rst b/docs/products/flink/concepts/flink-architecture.rst
index 19f7f3f20d..0f7a754aa7 100644
--- a/docs/products/flink/concepts/flink-architecture.rst
+++ b/docs/products/flink/concepts/flink-architecture.rst
@@ -19,9 +19,10 @@ Some of the responsibilities of the JobManager include:
 In a high-availability setup, there may be multiple JobManagers running in the cluster, with one JobManager designated as the leader and the others as standby JobManagers. 
 
 The JobManager in Apache Flink consists of three main components:
+
 -  **ResourceManager:** The ResourceManager is responsible for managing the allocation and deallocation of resources in the Flink cluster. Additionally, ResourceManger is responsible for managing **Task slots** - the unit of resource scheduling in a Flink cluster.
 -  **Dispatcher:** The Dispatcher in Apache Flink ensures tasks run smoothly on the cluster by scheduling them on available task slots and ensuring that tasks are executed efficiently. 
--  **JobMaster: ** The JobMaster in Apache Flink makes sure a specific job runs smoothly on the cluster by coordinating the tasks and executing them correctly and efficiently.
+-  **JobMaster:** The JobMaster in Apache Flink makes sure a specific job runs smoothly on the cluster by coordinating the tasks and executing them correctly and efficiently.
 
 TaskManager
 -----------
diff --git a/docs/products/flink/concepts/managed-service-features.rst b/docs/products/flink/concepts/managed-service-features.rst
index be33b913c7..716bc5f37b 100644
--- a/docs/products/flink/concepts/managed-service-features.rst
+++ b/docs/products/flink/concepts/managed-service-features.rst
@@ -25,7 +25,7 @@ For more information on available options, refer to `Apache Flink's fault tolera
 
 Disaster recovery
 -----------------
-Periodic checkpoints have been configured to be persisted externally in object storage. They allow Flink to recover states and positions in the streams by giving the application the same semantics as a failure-free execution. For information on checkpoints, see 
+Periodic checkpoints have been configured to be persisted externally in object storage. They allow Flink to recover states and positions in the streams by giving the application the same semantics as a failure-free execution. For information on checkpoints, see :doc:`Checkpoints <../concepts/checkpoints>`. 
 
 Security considerations
 -----------------------