fix anchors for config links take 2

fixes #260

Author: tarzanek

docs/source/migrate-from-cassandra-or-parquet.rst

@@ -2,7 +2,7 @@
 Migrate from Apache Cassandra or from a Parquet File
 ====================================================
 
-This page explains how to fill the ``source`` and ``target`` properties of the `configuration file <../configuration>`_ to migrate data:
+This page explains how to fill the ``source`` and ``target`` properties of the `configuration file </configuration>`_ to migrate data:
 
 - from Apache Cassandra, ScyllaDB, or from a `Parquet <https://parquet.apache.org/>`_ file,
 - to Apache Cassandra or ScyllaDB.
@@ -124,7 +124,7 @@ In case the object is not public in the S3 bucket, you can provide the AWS crede
 
 Where ``<access-key>`` and ``<secret-key>`` should be replaced with your actual AWS access key and secret key.
 
-The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference <../configuration/#aws-authentication>`__ for more details.
+The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference </configuration#aws-authentication>`__ for more details.
 
 ---------------------------
 Configuring the Destination

docs/source/migrate-from-dynamodb.rst

@@ -57,7 +57,7 @@ In practice, your source database (DynamoDB or Alternator) may require authentic
 
 Where ``<access-key>`` and ``<secret-key>`` should be replaced with your actual AWS access key and secret key.
 
-The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference <../configuration/#aws-authentication>`__ for more details.
+The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference </configuration#aws-authentication>`__ for more details.
 
 Last, you can provide the following optional properties:
 
@@ -150,7 +150,7 @@ Additionally, you can provide the following optional properties:
 
 Where ``<host>``, ``<port>``, ``<region>``, ``<access-key>``, and ``<secret-key>`` should be replaced with your specific values.
 
-The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference <../configuration/#aws-authentication>`__ for more details.
+The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference </configuration#aws-authentication>`__ for more details.
 
 ---------------------------
 Configuring the Destination
@@ -209,4 +209,4 @@ Additionally, you can also set the following optional properties:
 
 Where ``<host>``, ``<port>``, ``<region>``, ``<access-key>``, and ``<secret-key>`` are replaced with your specific values.
 
-The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference <../configuration/#aws-authentication>`__ for more details.
+The Migrator also supports advanced AWS authentication options such as using `AssumeRole <https://docs.aws.amazon.com/IAM/latest/UserGuide/tutorial_cross-account-with-roles.html>`_. Please read the `configuration reference </configuration#aws-authentication>`__ for more details.

docs/source/resume-interrupted-migration.rst

@@ -8,6 +8,6 @@ If, for some reason, the migration is interrupted (e.g., because of a networking
 
 Savepoints are configuration files that contain information about the already migrated items, which can be skipped when the migration is resumed. The savepoint files are automatically generated during the migration. To use a savepoint, start a migration using it as configuration file.
 
-You can control the savepoints location and the interval at which they are generated in the configuration file under the top-level property ``savepoints``. See `the corresponding section of the configuration reference </configuration/#savepoints>`__.
+You can control the savepoints location and the interval at which they are generated in the configuration file under the top-level property ``savepoints``. See `the corresponding section of the configuration reference </configuration#savepoints>`__.
 
 During the migration, the savepoints are generated with file names like ``savepoint_xxx.yaml``, where ``xxx`` is a timestamp looking like ``1234567890``. To resume a migration, start a new migration with the latest savepoint as configuration file.