Add disambiguation sections

Author: kodster28

src/content/docs/style-guide/documentation-content-strategy/content-types/design-guide.mdx

@@ -7,7 +7,13 @@ meta:
 
 ## Purpose
 
-Help users understand how to plan and design a solution using Cloudflare. Typically design guides are a subset of a reference architecture.
+Help users understand how to plan and design a solution using Cloudflare. Typically [design guides](/reference-architecture/design-guides/) are a subset of a [reference architecture](/reference-architecture/).
+
+:::note[Disambiguation]
+
+This page describes the content strategy for a design guide. For help with Cloudflare products, refer to [Design guides](/reference-architecture/design-guides/).
+
+:::
 
 ## Tone
 

src/content/docs/style-guide/documentation-content-strategy/content-types/implementation-guide.mdx

@@ -7,7 +7,13 @@ meta:
 
 ## Purpose
 
-Walk the reader through best practices for the implementation of a solution using Cloudflare.
+Walk the reader through best practices for the [implementation](/reference-architecture/implementation-guides/) of a solution using Cloudflare.
+
+:::note[Disambiguation]
+
+This page describes the content strategy for an implementation guide. For help with Cloudflare products, refer to [Implementation guides](/reference-architecture/implementation-guides/).
+
+:::
 
 ## Tone
 

src/content/docs/style-guide/documentation-content-strategy/content-types/reference-architecture-diagram.mdx

@@ -11,6 +11,12 @@ import { Render } from "~/components";
 
 To provide a visual reference and explanation of using Cloudflare for a specific solution.
 
+:::note[Disambiguation]
+
+This page describes the content strategy for a reference architecture diagram. For help with Cloudflare products, refer to [Reference archiectures diagrams](/reference-architecture/diagrams/).
+
+:::
+
 ## Tone
 
 instructional, straightforward

src/content/docs/style-guide/documentation-content-strategy/content-types/reference-architecture.mdx

@@ -9,10 +9,16 @@ import { Render } from "~/components";
 
 ## Purpose
 
-The purpose of a reference architecture is to provide a high-level view of how all or part of the Cloudflare platform is built and how Cloudflare products would fit into a customer's existing infrastructure. Reference architectures are designed to show where our platform fits in with a customer's current environment and describe key aspects of a Cloudflare feature/service. Reference architectures should also map customer use cases to Cloudflare solutions.
+The purpose of a [reference architecture](/reference-architecture/) is to provide a high-level view of how all or part of the Cloudflare platform is built and how Cloudflare products would fit into a customer's existing infrastructure. Reference architectures are designed to show where our platform fits in with a customer's current environment and describe key aspects of a Cloudflare feature/service. Reference architectures should also map customer use cases to Cloudflare solutions.
 
 Reference architectures are typically very detailed. To describe a single architecture without much written content, use a [Reference architecture diagram](/style-guide/documentation-content-strategy/content-types/reference-architecture-diagram/).
 
+:::note[Disambiguation]
+
+This page describes the content strategy for a reference architecture. For help with Cloudflare products, refer to [Reference archiectures](/reference-architecture/).
+
+:::
+
 ## Tone
 
 guiding, straightforward

src/content/docs/style-guide/documentation-content-strategy/content-types/tutorial.mdx

@@ -1,6 +1,8 @@
 ---
 pcx_content_type: concept
-title: Content type - Tutorial
+title: Tutorial
+meta:
+  title: Content type - Tutorial
 ---
 
 import { GlossaryDefinition, Render } from "~/components";