DOC-5282 fixed links in examples

Author: andy-stark-redis

content/integrate/redis-data-integration/data-pipelines/transform-examples/map-example.md

@@ -27,14 +27,14 @@ transformation.
 ## Map to a new JSON structure
 
 The first
-[job file]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#job-files" >}})
+[job file]({{< relref "/integrate/redis-data-integration/data-pipelines/transform-examples" >}})
 example creates a new [JSON]({{< relref "/develop/data-types/json" >}})
 object structure to write to the target.
 The `source` section selects the `employee` table of the
 [`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
 database (the optional `db` value here corresponds to the
 `sources.<source-name>.connection.database` value defined in
-[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
+[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
 
 In the `transform` section, the `map` transformation uses a [JMESPath](https://jmespath.org/)
 expression to specify the new JSON format. (Note that the vertical bar "|" in the `expression`

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-add-field-example.md

@@ -29,7 +29,7 @@ The `source` section selects the `customer` table of the
 [`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
 database (the optional `db` value here corresponds to the
 `sources.<source-name>.connection.database` value defined in
-[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
+[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
 
 In the `transform` section, the `add_field` transformation adds an extra field called `localphone`
 to the object, which is created by removing the country and area code from the `phone`

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-remove-field-example.md

@@ -29,7 +29,7 @@ The `source` section selects the `employee` table of the
 [`chinook`](https://github.com/Redislabs-Solution-Architects/rdi-quickstart-postgres)
 database (the optional `db` field here corresponds to the
 `sources.<source-name>.connection.database` field defined in
-[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}})).
+[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}})).
 
 In the `transform` section, the `remove_field` transformation removes the
 `hiredate` field.

content/integrate/redis-data-integration/data-pipelines/transform-examples/redis-string-example.md

@@ -24,7 +24,7 @@ The `title` is then written to the Redis target database as a string under a cus
 form `AlbumTitle:42`, where the `42` is the primary key value of the table (the `albumid` column).
 
 The `connection` is an optional parameter that refers to the corresponding connection name defined in
-[`config.yaml`]({{< relref "integrate/redis-data-integration/data-pipelines/data-pipelines#the-configyaml-file" >}}). 
+[`config.yaml`]({{< relref "/integrate/redis-data-integration/data-pipelines/pipeline-config" >}}). 
 When you specify the `data_type` parameter for the job, it overrides the system-wide setting `target_data_type` defined in `config.yaml`. Here, the `string` data type also requires an `args` subsection
 with a `value` argument that specifies the column you want to capture from the source table.