odpi/egeria#6907 master->main rename

Signed-off-by: Nigel Jones <[email protected]>

site/docs/concepts/audit-log-destination-connector.md

@@ -12,7 +12,7 @@ An [OMAG Server](/concepts/omag-server) can have [multiple audit log destination
 The implementation for the audit log destination connector can make further choices about how each log record is processed.
 
 The interface for audit log destination connectors is located in the
-[repository-services-apis](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/repository-services/repository-services-apis/src/main/java/org/odpi/openmetadata/repositoryservices/connectors/stores/auditlogstore) module.  The audit log destination connectors implemented by Egeria are described in the [connector catalog](/connectors/#audit-log-destination-connectors).
+[repository-services-apis](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/repository-services/repository-services-apis/src/main/java/org/odpi/openmetadata/repositoryservices/connectors/stores/auditlogstore) module.  The audit log destination connectors implemented by Egeria are described in the [connector catalog](/connectors/#audit-log-destination-connectors).
 
 
 ---8<-- "snippets/abbr.md"

site/docs/concepts/cohort-registry-store-connector.md

@@ -7,7 +7,7 @@
 
 
 The default file-based version of this connector is located in the
-[adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors)
+[adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors)
 module.
 
 ---8<-- "snippets/abbr.md"

site/docs/concepts/configuration-document-store-connector.md

@@ -14,7 +14,7 @@ Configuration documents may contain security certificates and passwords and so s
 
 
 ??? question "Configuration document store connector interface"
-The [admin-services-api :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/admin-services/admin-services-api){ target=gh } module provides the interface definition for this connector. Its interface is simple -- consisting of save, retrieve and delete operations:
+The [admin-services-api :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/admin-services/admin-services-api){ target=gh } module provides the interface definition for this connector. Its interface is simple -- consisting of save, retrieve and delete operations:
 
     ```java
     /**
@@ -50,12 +50,12 @@ The configuration document is represented by the `OMAGServerConfig` structure. T
 
 ### Sample implementations
 
-The implementations of this connector provided by Egeria are found in the [configuration-store-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors){ target=gh } module. There are two connectors:
+The implementations of this connector provided by Egeria are found in the [configuration-store-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors){ target=gh } module. There are two connectors:
 
-- [configuration-file-store-connector :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-file-store-connector){ target=gh } supports managing the open metadata configuration as a clear text JSON file.
-- [configuration-encrypted-file-store-connector :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-encrypted-file-store-connector){ target=gh } supports managing the open metadata configuration as an encrypted JSON file.
+- [configuration-file-store-connector :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-file-store-connector){ target=gh } supports managing the open metadata configuration as a clear text JSON file.
+- [configuration-encrypted-file-store-connector :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors/configuration-encrypted-file-store-connector){ target=gh } supports managing the open metadata configuration as an encrypted JSON file.
 
-It is also possible to [write your own implementation](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors){ target=gh }.
+It is also possible to [write your own implementation](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/configuration-store-connectors){ target=gh }.
 
 ### Configuring the connector
 

site/docs/concepts/connector-provider.md

@@ -17,7 +17,7 @@ hide:
 
 
 !!! example "Example: connector provider for the Kafka Monitor Integration Connector"
-    For example, the [`KafkaMonitorIntegrationProvider` :material-github:](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/adapters/open-connectors/integration-connectors/kafka-integration-connector/src/main/java/org/odpi/openmetadata/adapters/connectors/integration/kafka/KafkaMonitorIntegrationProvider.java){ target=gh } is used to instantiate connectors that are monitoring an Apache Kafka broker. Therefore, its name and description refer to Kafka, and the connectors it instantiates are of type [`KafkaMonitorIntegrationConnector :material-github:](https://github.com/odpi/egeria/blob/master/open-metadata-implementation/adapters/open-connectors/integration-connectors/kafka-integration-connector/src/main/java/org/odpi/openmetadata/adapters/connectors/integration/kafka/KafkaMonitorIntegrationConnector.java){ target=gh }.
+    For example, the [`KafkaMonitorIntegrationProvider` :material-github:](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/adapters/open-connectors/integration-connectors/kafka-integration-connector/src/main/java/org/odpi/openmetadata/adapters/connectors/integration/kafka/KafkaMonitorIntegrationProvider.java){ target=gh } is used to instantiate connectors that are monitoring an Apache Kafka broker. Therefore, its name and description refer to Kafka, and the connectors it instantiates are of type [`KafkaMonitorIntegrationConnector :material-github:](https://github.com/odpi/egeria/blob/main/open-metadata-implementation/adapters/open-connectors/integration-connectors/kafka-integration-connector/src/main/java/org/odpi/openmetadata/adapters/connectors/integration/kafka/KafkaMonitorIntegrationConnector.java){ target=gh }.
 
 
 

site/docs/concepts/connector-type.md

@@ -33,7 +33,7 @@ The connector type is linked to the [Connection](/concepts/connection) objects t
 !!! education "Further information"
 
     - The open metadata type for a connector type is defined in [model 0201](/types/2/0201-Connectors-and-Connections).
-    - The [open connector archives](https://github.com/odpi/egeria/tree/master/open-metadata-resources/open-metadata-archives/open-connector-archives)  module provides an open metadata archive that contains connector types for data connectors supported by Egeria.
+    - The [open connector archives](https://github.com/odpi/egeria/tree/main/open-metadata-resources/open-metadata-archives/open-connector-archives)  module provides an open metadata archive that contains connector types for data connectors supported by Egeria.
 
 
---8<-- "snippets/abbr.md"
+--8<-- "snippets/abbr.md"

site/docs/concepts/connector.md

@@ -51,11 +51,11 @@ The table below lists the different types of connectors supported by Egeria's se
 | Configuration Document Store  | Persists the [configuration document](/concepts/configuration-document/#storage) for an OMAG Server. | [Building Configuration Document Store Connectors](/guides/developer/runtime-connectors/configuration-document-store-connector) | [Configuration Document Store Catalog](/connectors/#configuration-document-store-connectors) |
 | Platform Security Connector   | Manages [service authorization](/features/metadata-security) for the OMAG Server Platform. | [Building Platform Metadata Security Connectors](/guides/developer/runtime-connectors/) | [Platform Metadata Security Connector Catalog](/connectors/#platform-metadata-security-connectors) |
 | Server Security Connector     | Manages [service and metadata instance authorization](/features/metadata-security) for an OMAG Server. | [Building Server Metadata Security Connectors](/guides/developer/runtime-connectors/server-metadata-security-connector) | [Server Metadata Security Connector Catalog](/connectors/#server-metadata-security-connectors) |
-| Open Metadata Archive Store   | Reads an open metadata archive from a particular type of store. | [OMRS Open Metadata Archive Store Connector](/concepts/open-metadata-archive-store-connector) | [open-metadata-archive-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-archive-connectors){ target=gh } |
-| Audit Log Store               | Audit logging destination | [OMRS Audit Log Store Connector](/concepts/audit-log-store-connector) | [audit-log-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/audit-log-connectors){ target=gh } |
-| Cohort Registry Store         | Local store of membership of an [open metadata repository cohort](/concepts/cohort-member). | [Building Cohort Registry Store Connectors](/guides/developer/runtime-connectors/cohort-registry-store-connector) | [cohort-registry-store-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors){ target=gh } |
-| Open Metadata Topic Connector | Sends and received events on a topic hosted by an external [event bus](/concepts/event-bus) such as Apache Kafka. | [Building Open Metadata Topic Connectors](/concepts/open-metadata-topic-connector) | [open-metadata- topic-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/event-bus-connectors/open-metadata-topic-connectors){ target=gh } |
-| Metadata Collection (repository) Store | Interfaces with a metadata repository API for retrieving and storing metadata. | [OMRS Repository Connectors](/concepts/repository-connector)| [open-metadata-collection-store-connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors){ target=gh } |
+| Open Metadata Archive Store   | Reads an open metadata archive from a particular type of store. | [OMRS Open Metadata Archive Store Connector](/concepts/open-metadata-archive-store-connector) | [open-metadata-archive-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-archive-connectors){ target=gh } |
+| Audit Log Store               | Audit logging destination | [OMRS Audit Log Store Connector](/concepts/audit-log-store-connector) | [audit-log-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/audit-log-connectors){ target=gh } |
+| Cohort Registry Store         | Local store of membership of an [open metadata repository cohort](/concepts/cohort-member). | [Building Cohort Registry Store Connectors](/guides/developer/runtime-connectors/cohort-registry-store-connector) | [cohort-registry-store-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/cohort-registry-store-connectors){ target=gh } |
+| Open Metadata Topic Connector | Sends and received events on a topic hosted by an external [event bus](/concepts/event-bus) such as Apache Kafka. | [Building Open Metadata Topic Connectors](/concepts/open-metadata-topic-connector) | [open-metadata- topic-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/event-bus-connectors/open-metadata-topic-connectors){ target=gh } |
+| Metadata Collection (repository) Store | Interfaces with a metadata repository API for retrieving and storing metadata. | [OMRS Repository Connectors](/concepts/repository-connector)| [open-metadata-collection-store-connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors){ target=gh } |
 | Metadata Collection (repository) Event Mapper | Maps events from a third party metadata repository to open metadata events. | [OMRS Event Mappers](/concepts/event-mapper-connector) | none |
 
 

site/docs/concepts/data-engine-proxy.md

@@ -12,7 +12,7 @@ The *data engine proxy* is a [governance server](/concepts/governance-server) th
 
 ![Data Engine Proxy](data-engine-proxy.svg)
 
-The data engine proxy is paired with the [Data Engine OMAS](/services/omas/data-engine/overview). Its connector interfaces are defined in the [data-engine-proxy-connector :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/governance-servers/data-engine-proxy-services/data-engine-proxy-connector){ target=gh } module.
+The data engine proxy is paired with the [Data Engine OMAS](/services/omas/data-engine/overview). Its connector interfaces are defined in the [data-engine-proxy-connector :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/governance-servers/data-engine-proxy-services/data-engine-proxy-connector){ target=gh } module.
 
 !!! education "Further information"
     - [Setting up the data engine proxy](/guides/admin/configuring-a-data-engine-proxy-server)

site/docs/concepts/omag-server-platform.md

@@ -30,7 +30,7 @@ The OMAG Server Platform can host multiple OMAG Servers at any one time and a si
 - **B** - Multiple OMAG Servers are hosted on the same OMAG Server Platform. The OMAG Server Platform routes inbound requests to the right server based on the server name specified in the request URL. The servers may all be of the same type offering the same services but to different groups of people or be a set of collaborating servers of different types consolidated onto the same platform.
 - **C** - Multiple copies of same server instance each running on different platforms to provide high availability and distribution of workload (horizontal scalability).
 
-The OMAG Server platform is included in the [Egeria Distribution TAR file](https://github.com/odpi/egeria/tree/master/open-metadata-distribution/open-metadata-assemblies)
+The OMAG Server platform is included in the [Egeria Distribution TAR file](https://github.com/odpi/egeria/tree/main/open-metadata-distribution/open-metadata-assemblies)
 which can be installed on your machine by following the [Installing Egeria Tutorial](/education/tutorials/building-egeria-tutorial/task-installing-egeria).
 
 ??? education "Further reading"

site/docs/concepts/plugin-repository-proxy.md

@@ -20,6 +20,6 @@ The plugin repository proxy hosts a repository connector to wrap the non-Egeria
 There are two plugin repository connector implementations included with Egeria:
 
 - [XTDB repository connector :material-github:](https://github.com/odpi/egeria-connector-xtdb){ target=xtdb }
-- [JanusGraph repository connectors :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector){ target=janus }
+- [JanusGraph repository connectors :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/repository-services-connectors/open-metadata-collection-store-connectors/graph-repository-connector){ target=janus }
 
 --8<-- "snippets/abbr.md"

site/docs/connectors/governance-action/governance-action-service-intro.md

@@ -24,7 +24,7 @@ It is possible to implement complex governance actions in a single governance ac
 
 * *[Provisioning Governance Action Service](/guides/developer/governance-action-services/overview/#provisioning-governance-action-service)*  invokes a provisioning service whenever a provisioning request is made.  Typically, the provisioning service is an external service.  It may also create lineage metadata to describe the work of the provisioning service if the provisioning service is not able to create lineage itself.
 
-The interfaces for governance action services is defined in the [governance-action-framework :material-github:](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/frameworks/governance-action-framework) module.
+The interfaces for governance action services is defined in the [governance-action-framework :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/frameworks/governance-action-framework) module.
 
 ??? education "Governance action service example - data onboarding process"
 
@@ -74,4 +74,4 @@ The interfaces for governance action services is defined in the [governance-acti
 
     Since the watchdog governance action service calls the provisioning governance action process explicitly via the governance action, their implementations are somewhat tied together.  The alternative is that the watchdog governance action service can invoke a [governance action process](/concepts/governance-action-process) that will choreograph the execution of one or more governance services based on a flow definition managed in open metadata.  The governance action process separates the implementation of the watchdog governance action service from the follow-on governance actions since changes to the follow-on processing is maintained through open metadata rather than requiring code changes to the watchdog governance action service code.
 
---8<-- "snippets/abbr.md"
+--8<-- "snippets/abbr.md"

site/docs/connectors/governance-action/origin-seeker-remediation-governance-action-service.md

@@ -9,7 +9,7 @@
     - Connector Category: [Remediation Governance Action Service](/concepts/governance-service)
     - Hosting Service: [Governance Action OMES](/services/omes/governance-action/overview)
     - Hosting Server: [Engine Host](/concepts/engine-host)
-    - Source Module: [governance-action-connectors](https://github.com/odpi/egeria/tree/master/open-metadata-implementation/adapters/open-connectors/governance-action-connectors)
+    - Source Module: [governance-action-connectors](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/adapters/open-connectors/governance-action-connectors)
     - Jar File Name: `governance-action-connectors.jar`
     - ConnectorProviderClassName: `org.odpi.openmetadata.adapters.connectors.governanceactions.remediation.OriginSeekerGovernanceActionProvider`
 
@@ -107,4 +107,4 @@ This governance action service could be enhanced as follows:
 
 ----
 License: [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/),
-Copyright Contributors to the ODPi Egeria project.
+Copyright Contributors to the ODPi Egeria project.