Updated examples with one k8s-docs since the deployment specs are sam…

…e for all connectors.

examples/db2/README.md

@@ -6,7 +6,7 @@ Please see an example under [Demo](demo/setup_db2.sh).
 
 Before using Redis Connect to capture the changes committed on DB2 into Redis Enterprise Databases, first create a database for the metadata management and metrics provided by Redis Connect by creating a database with [RedisTimeSeries](https://redis.com/modules/redis-timeseries/) module enabled, see [Create Redis Enterprise Database](https://docs.redis.com/latest/rs/administering/creating-databases/#creating-a-new-redis-database) for reference. Then, create (or use an existing) another Redis Enterprise database (Target) to store the changes coming from PostgreSQL. Additionally, you can enable [RediSearch 2.0](https://redis.com/blog/introducing-redisearch-2-0/) module on the target database to enable secondary index with full-text search capabilities on the existing hashes where PostgreSQL changed events are being written at then [create an index, and start querying](https://oss.redis.com/redisearch/Commands/) the document in hashes.
 
-| ℹ️                                          |
-|:--------------------------------------------|
-| Docker demo: Follow the [Docker demo](demo) |
-| K8s Setup: Follow the [k8s-docs](k8s-docs)  |
+| ℹ️                                               |
+|:-------------------------------------------------|
+| Docker demo: Follow the [Docker demo](demo)      |
+| K8s Setup: Follow the [k8s-docs](../../k8s-docs) |

examples/mongodb/README.md

@@ -6,7 +6,7 @@ Please see <a href="https://debezium.io/documentation/reference/stable/connector
 
 Before using Redis Connect to capture the changes committed on SQL Server into Redis Enterprise Database, first create a database for the metadata management and metrics provided by Redis Connect by creating a database with [RedisTimeSeries](https://redislabs.com/modules/redis-timeseries/) module enabled, see [Create Redis Enterprise Database](https://docs.redislabs.com/latest/rs/administering/creating-databases/#creating-a-new-redis-database) for reference. Then, create (or use an existing) another Redis Enterprise database (Target) to store the changes coming from SQL Server. Additionally, you can enable [RediSearch 2.0](https://redislabs.com/blog/introducing-redisearch-2-0/) module on the target database to enable secondary index with full-text search capabilities on the existing hashes where SQL Server changed events are being written at then [create an index, and start querying](https://oss.redislabs.com/redisearch/Commands/) the document in hashes.
 
-| ℹ️                                          |
-|:--------------------------------------------|
-| Docker demo: Follow the [Docker demo](demo) |
-| K8s Setup: Follow the [k8s-docs](k8s-docs)  |
+| ℹ️                                               |
+|:-------------------------------------------------|
+| Docker demo: Follow the [Docker demo](demo)      |
+| K8s Setup: Follow the [k8s-docs](../../k8s-docs) |

examples/mssql/README.md

@@ -8,7 +8,7 @@ Please see an example under [Demo](demo/setup_mssql.sh).
 
 Before using Redis Connect to capture the changes committed on SQL Server into Redis Enterprise Database, first create a database for the metadata management and metrics provided by Redis Connect by creating a database with [RedisTimeSeries](https://redislabs.com/modules/redis-timeseries/) module enabled, see [Create Redis Enterprise Database](https://docs.redislabs.com/latest/rs/administering/creating-databases/#creating-a-new-redis-database) for reference. Then, create (or use an existing) another Redis Enterprise database (Target) to store the changes coming from SQL Server. Additionally, you can enable [RediSearch 2.0](https://redislabs.com/blog/introducing-redisearch-2-0/) module on the target database to enable secondary index with full-text search capabilities on the existing hashes where SQL Server changed events are being written at then [create an index, and start querying](https://oss.redislabs.com/redisearch/Commands/) the document in hashes.
 
-| ℹ️                                          |
-|:--------------------------------------------|
-| Docker demo: Follow the [Docker demo](demo) |
-| K8s Setup: Follow the [k8s-docs](k8s-docs)  |
+| ℹ️                                               |
+|:-------------------------------------------------|
+| Docker demo: Follow the [Docker demo](demo)      |
+| K8s Setup: Follow the [k8s-docs](../../k8s-docs) |