OSDU-(C)/Reference-Architecture.md

@@ -3,7 +3,7 @@ This is a collaboration space to define a reference architecture to carry forwar
 ## [Principles & Tenets](/OSDU-\(C\)/Reference-Architecture/Principles)
 The principles of the data ecosystem help us make architectural and technical choices that are consistent with our values, over time and across geography.
 
-## [Journey's](/OSDU-\(C\)/Reference-Architecture/Journey's)
+## [Journeys](/OSDU-\(C\)/Reference-Architecture/Journey's)
 These are the significant use cases that drive the architecture definition.
 
 ## [Functional Architecture](/OSDU-\(C\)/Reference-Architecture/Functional-Architecture)
@@ -16,10 +16,10 @@ Non-functional requirements of a system often have a larger impact on architectu
 These are the architectural decisions that are deemed important to produce a coherent system.  They are derived from principles, tenets, requirements but are more prescriptive.
 
 ## [Architectural Style](/OSDU-\(C\)/Reference-Architecture/Style)
-The data ecosystem architectural style is Microservices. This section describes our opinion on what a microservices architecture is.
+The data ecosystem architectural style is Microservices. This section describes our opinion on what a Microservices architecture is.
 
 ## [Conceptual Architecture](/OSDU-\(C\)/Reference-Architecture/Conceptual-Architecture)
-This view breaks down the architecture into it's service components.  Because we adhere to domain driven design, the Conceptual architecture mirrors the functional architecture.
+This view breaks down the architecture into it's service components.  Because we adhere to domain driven design, the conceptual architecture mirrors the functional architecture.
 
 ## [System Context](/OSDU-\(C\)/Reference-Architecture/Context)
 This positions the architecture in context of the other systems and workflows that interact with the data ecosystem.