fix(docs): edit text to link (datahub-project#6798)

CybercentreCanada · Feb 1, 2023 · c6d598d · c6d598d
1 parent 3c96513
commit c6d598d
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/docs/architecture/metadata-ingestion.md b/docs/architecture/metadata-ingestion.md
@@ -10,7 +10,7 @@ The figure below describes all the options possible for connecting your favorite
 
 ## Metadata Change Proposal: The Center Piece 
 
-The center piece for ingestion are [Metadata Change Proposals] which represent requests to make a metadata change to an organization's Metadata Graph. 
+The center piece for ingestion are [Metadata Change Proposal]s which represent requests to make a metadata change to an organization's Metadata Graph. 
 Metadata Change Proposals can be sent over Kafka, for highly scalable async publishing from source systems. They can also be sent directly to the HTTP endpoint exposed by the DataHub service tier to get synchronous success / failure responses. 
 
 ## Pull-based Integration
@@ -28,6 +28,7 @@ As long as you can emit a [Metadata Change Proposal (MCP)] event to Kafka or mak
 DataHub comes with a Spring job, [mce-consumer-job], which consumes the Metadata Change Proposals and writes them into the DataHub Metadata Service (datahub-gms) using the `/ingest` endpoint. 
 
 [Metadata Change Proposal (MCP)]: ../what/mxe.md#metadata-change-proposal-mcp
+[Metadata Change Proposal]: ../what/mxe.md#metadata-change-proposal-mcp
 [Metadata Change Log (MCL)]: ../what/mxe.md#metadata-change-log-mcl
 [equivalent Pegasus format]: https://linkedin.github.io/rest.li/how_data_is_represented_in_memory#the-data-template-layer
 [mce-consumer-job]: ../../metadata-jobs/mce-consumer-job

diff --git a/docs/architecture/metadata-serving.md b/docs/architecture/metadata-serving.md
@@ -25,7 +25,7 @@ Note that not all MCP-s will result in an MCL, because the DataHub serving tier
 
 ### Metadata Index Applier (mae-consumer-job)
 
-[Metadata Change Logs]s are consumed by another Spring job, [mae-consumer-job], which applies the changes to the [graph] and [search index] accordingly.
+[Metadata Change Log]s are consumed by another Spring job, [mae-consumer-job], which applies the changes to the [graph] and [search index] accordingly.
 The job is entity-agnostic and will execute corresponding graph & search index builders, which will be invoked by the job when a specific metadata aspect is changed. 
 The builder should instruct the job how to update the graph and search index based on the metadata change.