From 6c4e3aa4d7eda53946c490b52f2257415161d409 Mon Sep 17 00:00:00 2001 From: Mandy Chessell Date: Tue, 9 Nov 2021 13:59:11 +0000 Subject: [PATCH] Fix links Signed-off-by: Mandy Chessell --- .../guides/diagnostic/examples-of-server-start-up-errors.md | 4 ++-- site/docs/introduction/key-concepts.md | 2 +- site/docs/services/server-chassis.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/site/docs/guides/diagnostic/examples-of-server-start-up-errors.md b/site/docs/guides/diagnostic/examples-of-server-start-up-errors.md index ad166956ed..7d8d4dd09b 100644 --- a/site/docs/guides/diagnostic/examples-of-server-start-up-errors.md +++ b/site/docs/guides/diagnostic/examples-of-server-start-up-errors.md @@ -173,7 +173,7 @@ Caused by: org.apache.kafka.common.errors.TimeoutException: Timed out waiting fo * [Integration Daemon Diagnostic Guide](integration-daemon-diagnostic-guide.md) covers specific guidance on diagnosing and fixing errors in the Integration Daemon. -* [Repository Services Design Overview](/egeria-docs/servvices/omrs) describes the different repository services subsystems used in the different types of OMAG Servers. -* [Repository Services Start up Design](/egeria-docs/servvices/omrs/subsystem-descriptions) describe the components initialized in an Egeria Metadata Server. +* [Repository Services Design Overview](/egeria-docs/services/omrs) describes the different repository services subsystems used in the different types of OMAG Servers. +* [Repository Services Start up Design](/egeria-docs/services/omrs/subsystem-descriptions) describe the components initialized in an Egeria Metadata Server. ---8<-- "snippets/abbr.md" diff --git a/site/docs/introduction/key-concepts.md b/site/docs/introduction/key-concepts.md index 9dce893ab3..5b923b2933 100644 --- a/site/docs/introduction/key-concepts.md +++ b/site/docs/introduction/key-concepts.md @@ -129,7 +129,7 @@ There should be, at most, a *tiny* chance[^3] that two servers will generate the Adhering to these concepts and the principles by which they behave is the subject of *conformance*. Egeria provides an [automated testing suite to validate that a given repository or third party integration behaves according to these expectations](/egeria-docs/guides/cts/overview), the successful completion of which is a necessary input to a tool being granted the use of an Egeria conformance mark. -[^1]: You may want to see the [cohort interactions walkthrough](/egeria-docs/features/cohort-operaation/overview) for more details on how cohort participants interact. +[^1]: You may want to see the [cohort interactions walkthrough](/egeria-docs/features/cohort-operation/overview) for more details on how cohort participants interact. [^2]: You may want to see the [OMRS metamodel](/egeria-docs/guides/developer/repository-connectors/metamodel/overview) for more details on the granularity of metadata exchange. [^3]: The rarity will depend on the specific algorithm used, but as an example the algorithm used within Egeria generates type 4 UUIDs, for which the [probability of a collision is so small that it can almost be ignored :material-dock-window:](https://en.wikipedia.org/wiki/Universally_unique_identifier#Collisions){ target=wiki }. But as it is not *impossible*, Egeria does still provide the mechanisms to detect and resolve such conflicts. diff --git a/site/docs/services/server-chassis.md b/site/docs/services/server-chassis.md index 9e96c968cf..29e8dd8a52 100644 --- a/site/docs/services/server-chassis.md +++ b/site/docs/services/server-chassis.md @@ -115,7 +115,7 @@ To make a new Java package visible to **OMAGServerPlatform**, add its **spring** to the **pom.xml** file for **server-chassis-spring** and it will be picked up in the component scan. For example, this is the snippet of XML in the pom.xml file that adds the -[Asset Owner OMAS](/egeria-docs/servvices/omas/asset-owner/overview) services +[Asset Owner OMAS](/egeria-docs/services/omas/asset-owner/overview) services to the OMAG server platform. ```xml