diff --git a/site/docs/types/4/0462-Governance-Action-Processes.md b/site/docs/types/4/0462-Governance-Action-Processes.md
index 548f199138..9544a27f5c 100644
--- a/site/docs/types/4/0462-Governance-Action-Processes.md
+++ b/site/docs/types/4/0462-Governance-Action-Processes.md
@@ -58,7 +58,7 @@ GovernanceActionProcessStep is a *GovernanceActionType* and so has all of the at
* *ignoreMultipleTriggers* - indicates that a governance action should only be triggered once from this governance action process step, no matter how many times the appropriate guards are produced. This is important for long-running governance actions that may be triggered by multiple instances of previous steps but is held waiting for the mandatory guard.
-## NextGovernanceProcessStep
+## NextGovernanceProcessStep relationship
The *NextGovernanceProcessStep* relationship identifies the next step in the process flow.
@@ -67,6 +67,11 @@ The *NextGovernanceProcessStep* relationship identifies the next step in the pro
The follow-on action runs when all of its mandatory guards are produced by previous steps. It runs as many times as a matching guard is produced unless ignoreMultipleTriggers is set in which case it will run once for that guard.
+## GovernanceActionProcessInstance entity
+
+The *GovernanceActionProcessInstance* entity describes a running instance of a *GovernanceActionProcess*. It is linked to its process using the [ProcessHierarchy](/types/2/0215-Software-Components) relationship.
+
+
???+ deprecated "Deprecated types"
The *ignoreMultipleTriggers* attribute in the *NextGovernanceProcessStep* has been deprecated. It is now located in the *GovernanceActionType* entity.
The *supportedGuards* attribute in the *GovernanceActionType* has been deprecated in favour of the *producedGuards* entity.
diff --git a/site/docs/types/4/0462-Governance-Action-Processes.svg b/site/docs/types/4/0462-Governance-Action-Processes.svg
index 6d70f70ddb..2a40917f33 100644
--- a/site/docs/types/4/0462-Governance-Action-Processes.svg
+++ b/site/docs/types/4/0462-Governance-Action-Processes.svg
@@ -1,4 +1,4 @@
-
\ No newline at end of file
+
\ No newline at end of file
diff --git a/site/docs/types/4/area-4-governance.drawio b/site/docs/types/4/area-4-governance.drawio
index c9601f0b0b..926b2d934b 100644
--- a/site/docs/types/4/area-4-governance.drawio
+++ b/site/docs/types/4/area-4-governance.drawio
@@ -2278,7 +2278,7 @@
-
+
@@ -2286,7 +2286,7 @@
-
+
@@ -2417,34 +2417,34 @@
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
-
+
@@ -2454,25 +2454,25 @@
-
+
-
+
-
+
-
+
-
+
-
+
@@ -2481,6 +2481,21 @@
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/site/snippets/release-notes/5-1.md b/site/snippets/release-notes/5-1.md
index f1f779a9eb..aa88e92643 100644
--- a/site/snippets/release-notes/5-1.md
+++ b/site/snippets/release-notes/5-1.md
@@ -10,10 +10,13 @@ _**These are DRAFT release notes. The notes will be updated until & when 5.1 is
* The [CatalogTarget](/types/4/0464-Dynamic-Integration-Groups) relationship is now multi-link which means it is possible to have multiple instances of this relationship between the same two entities. It also has two new attributes: *permittedSynchronization* and *deleteMethod*.
* The [DataAssetEncoding](/types/2/0210-Data-Stores) classification, that attaches to a [DataAsset](/types/0/0010-Base-Model), replaces the [DataStoreEncoding](/types/2/0210-Data-Stores) classification. The *DataStoreEncoding* is deprecated.
* There is a new type of entity called [VirtualRelationalTable](/types/2/0235-Information-View) for representing virtualized tables.
- * There are two new relationships relating to [governance actions](/concepts/governance-action). [TargetForActionType](/types/4/0462-Governance-Action-Processes) and [TargetForActionProcess](/types/4/0462-Governance-Action-Processes) allow targets for action to be pre-defined for a governance action type or governance action process respectively. The [GovernanceActionProcessFlow](/types/4/0462-Governance-Action-Processes) relationship receives a new property called `requestParameters`.
+ * There are two new relationships relating to [governance actions](/concepts/governance-action). [TargetForActionType](/types/4/0462-Governance-Action-Processes) and [TargetForActionProcess](/types/4/0462-Governance-Action-Processes) allow targets for action to be pre-defined for a governance action type or governance action process respectively. The [GovernanceActionProcessFlow](/types/4/0462-Governance-Action-Processes) relationship receives a new property called `requestParameters`. Finally, there is a new entity type called [GovernanceActionProcessInstance](/types/4/0462-Governance-Action-Processes) that represents a running instance of a Governance Action Process. It captures the start and end time of the process's execution.
??? functional "Unity Catalog Support"
* There are new [survey services and integration connectors](/connectors/unity-catalog) to support the new open-source Unity Catalog (UC).
-
+
+??? functional "Smarter integration daemon"
+ * In addition to the regular refreshes, the integration daemon will refresh an integration connector whenever a new catalog target is attached.
+
diff --git a/site/snippets/tasks/task-starting-omag-server-platform-from-jar.md b/site/snippets/tasks/task-starting-omag-server-platform-from-jar.md
index 015b8ce01f..45202b8e61 100644
--- a/site/snippets/tasks/task-starting-omag-server-platform-from-jar.md
+++ b/site/snippets/tasks/task-starting-omag-server-platform-from-jar.md
@@ -17,6 +17,13 @@ The OMAG Server Platform is started with the `java` command.
??? tip "Checking your Java installation"
Ensure you have a Java runtime at Version 17 or above installed on your machine. Check the version of Java you have with the command **java -version** and [install the appropriate version](/education/tutorials/building-egeria-tutorial/task-installing-java) if needed. You only need the JRE but select the JDK if you expect to also write some Java code.
+??? danger "MacOS users - XTDB hang, or platform exit due to mismatch crypto library"
+ On the latest level of the MacOs operating system we have experienced hangs during server startup, or the OMAG Server Platform exiting with a message complaining about the unsafe load of a cryptographic library. A question has been raised with the XTDB community to find out more about this library. In the meantime, there is a workaround if you see this issue: set the following environment variables before starting your OMAG Server Platform. This switches XTDB to using its own cryptography libraries.
+
+ ```properties
+ XTDB_DISABLE_LIBCRYPTO=True;XTDB_ENABLE_BYTEUTILS_SHA1=True
+ ```
+
Start the OMAG server platform with the following command:
```bash