Changes made 1as a result of review feedback

Signed-off-by: pcnorth <120174435+pcnorth@users.noreply.github.com>

content/developers/api-reference/assets-api/index.md

@@ -252,7 +252,7 @@ To fetch all Assets that use a specific Proof Mechanism, `GET` the Assets resour
 ```bash
 curl -g -v -X GET \
      -H "@$HOME/.datatrails/bearer-token.txt" \
-     "https://app.datatrails.ai/archivist/v2/assets?attributes.proof_mechanism=simple_hash"
+     "https://app.datatrails.ai/archivist/v2/assets?proof_mechanism=MERKLE_LOG"
 ```
 
 #### Fetch Events Ordered for SIMPLEHASHV1 Schema

content/glossary/common-datatrails-terms/index.md

@@ -45,7 +45,7 @@ Select a term for more information.
 | [organization](/platform/administration/verified-domain/)| any entity with a distinct DataTrails account who publishes or verifies provenance information on the platform|
 | [principal_accepted](/platform/overview/advanced-concepts/#user-principals-on-events)| the actual user principal information belonging to the credential used to access the DataTrails REST interface|
 | [principal_declared](/platform/overview/advanced-concepts/#user-principals-on-events)| an optional user-supplied value that tells who performed an Event|
-| [proof mechanism](/platform/overview/core-concepts/#proof-mechanisms)           | method by which information to the DataTrails distributed ledger can be verified                                                                              |
+| [proof mechanism](/platform/overview/core-concepts/#proving-provenance)           | method by which information to the DataTrails distributed ledger can be verified                                                                              |
 | [provenance](https://en.wiktionary.org/wiki/provenance) | the version and ownership history of a piece of data. With DataTrails this is an immutable audit trail to prove Who Did What When to any piece of data  |
 | [public asset](/platform/overview/public-attestation/)        | Assets that can be used to publicly assert data, accessible by URL without the need for a DataTrails account                                                   |
 | [selector](/platform/overview/creating-an-asset/#creating-an-asset)            | identifying attribute the Yaml Runner will use to check if your Asset exists already before attempting to create it  |

content/platform/overview/core-concepts/index.md

@@ -37,7 +37,7 @@ Events are things that happen during an Asset's lifecycle. Each Event Record con
 
 Events can never be deleted or modified. Events provide details on Asset attributes, such as updating the weight of a shipment, and/or details about the event itself, such as a recording a new document version.
 
-## Proof Mechanisms
+## Proving Provenance
 
 Artifacts and Events are core to the DataTrails platform, and being able to quickly demonstrate proof that these artifacts have not been tampered is key to knowing the information is secure and trustworthy.
 

content/platform/overview/registering-a-document-profile-asset/index.md

@@ -134,7 +134,7 @@ In the file you created earlier, begin adding metadata for your Asset:
    * `Document Type` - This is the class of the object; while it is arbitrary, it is best to have consistency amongst the type of Documents you use i.e. if it is a purchase order, the type could be `Purchase Order`, which will then be pre-populated for future Documents to use as their own types.
    * `Proof Mechanism` - The method used to record the transaction to the DataTrails distributed ledger.
 
-    Please see our [Advanced Concepts](/platform/overview/core-concepts/#proof-mechanisms) section for more information on the Proof Mechanism for your Document
+    Please see our [Core Concepts](/platform/overview/core-concepts/#proving-provenance) section for more information on the Proof Mechanism for your Document
 {{< tabs name="add_asset_details_min" >}}
 {{{< tab name="UI" >}}
 {{< img src="RegDocAdvancedOptions.png" alt="Rectangle" caption="<em>Advanced Options</em>" class="border-0" >}}