Addressed broken links comments

gchq · Sep 13, 2023 · 0dcd568 · 0dcd568
1 parent 95f4f79
commit 0dcd568
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/docs/change-notes/migrating-from-v1-to-v2/deprecations.md b/docs/change-notes/migrating-from-v1-to-v2/deprecations.md
@@ -40,7 +40,7 @@ In both serialisers, the method `deserialise(byte[])` has been marked as depreca
 ## Removal of Seed Matching
 
 ### [`operation.SeedMatching`](https://github.com/gchq/Gaffer/blob/gaffer2-1.21.1/core/operation/src/main/java/uk/gov/gchq/gaffer/operation/SeedMatching.java)
-SeedMatching has been removed from Gaffer. This was previously used in [get](../../reference/operations-guide/get.md) operations, like [`GetElements`](../../reference/operations-guide/get.md#getelements),, to select whether you wanted your results to contain only Elements that are the same type as the seed, or both Edges and Entities. For more info, see the Gaffer 1.X docs page on [SeedMatching](https://gchq.github.io/gaffer-doc/v1docs/getting-started/user-guide/filtering.html#seedmatching). As described in the Gaffer 1.X docs, `SeedMatching` can be replaced with a `View`. The default behaviour in Gaffer is the same as if you used `seed_matching="RELATED"`, so **if this is the case, there is no migration required**. However, if you used `seed_matching="EQUAL"`, you will need to migrate to a `View`.
+SeedMatching has been removed from Gaffer. This was previously used in [get](../../reference/operations-guide/get.md) operations, like [`GetElements`](../../reference/operations-guide/get.md#getelements), to select whether you wanted your results to contain only Elements that are the same type as the seed, or both Edges and Entities. For more info, see the Gaffer 1.X docs page on [SeedMatching](https://gchq.github.io/gaffer-doc/v1docs/getting-started/user-guide/filtering.html#seedmatching). As described in the Gaffer 1.X docs, `SeedMatching` can be replaced with a `View`. The default behaviour in Gaffer is the same as if you used `seed_matching="RELATED"`, so **if this is the case, there is no migration required**. However, if you used `seed_matching="EQUAL"`, you will need to migrate to a `View`.
 ??? example "SeedMatching migration with EdgeSeeds"
 
     Where SeedMatching was used to only get back Edges from EdgeSeeds

diff --git a/docs/development-guide/example-deployment/using-the-api.md b/docs/development-guide/example-deployment/using-the-api.md
@@ -188,4 +188,4 @@ asking, *"get all the `Created` edges on node `v1` that have a `weight` greater
 !!! tip
     As you can see filtering is based around predicates which are similar to if else statements in
     traditional programming. For a full list of available predicates refer to the reference
-    [documentation](../../reference//predicates-guide/predicates.md)
+    [documentation](../../reference/predicates-guide/predicates.md).
diff --git a/docs/reference/operations-guide/misc.md b/docs/reference/operations-guide/misc.md
@@ -49,7 +49,7 @@ Gets data from an endpoint. [Javadoc](https://gchq.github.io/Gaffer/uk/gov/gchq/
 
 Determines a "score" for an OperationChain. This is used to determine whether a particular user has the required permissions to execute a given OperationChain. [Javadoc](https://gchq.github.io/Gaffer/uk/gov/gchq/gaffer/operation/impl/ScoreOperationChain.html)
 
-This operation requires Store configuration to be set before it can be used. See the [Store Guide](../../administration-guide/gaffer-stores/store-guide.md) for how to do this.
+This operation requires Store configuration to be set before it can be used. See the [Store Guide](../../administration-guide/gaffer-stores/store-guide.md#scoreoperationchain) for how to do this.
 
 ### Example ScoreOperationChain