diff --git a/content/v2.0-preview/composition/composite-resource-definitions.md b/content/v2.0-preview/composition/composite-resource-definitions.md
index 8ad20b4d..9c4b8beb 100644
--- a/content/v2.0-preview/composition/composite-resource-definitions.md
+++ b/content/v2.0-preview/composition/composite-resource-definitions.md
@@ -38,7 +38,6 @@ Creating a CompositeResourceDefinition consists of:
 * [Defining a custom API schema and version](#xrd-versions).
   
 Optionally, CompositeResourceDefinitions also support:
-* [Defining connection secrets](#manage-connection-secrets).
 * [Setting composite resource defaults](#set-composite-resource-defaults).
  
 Composite resource definitions (`XRDs`) create new API endpoints inside a
@@ -397,7 +396,7 @@ field indicates which version of the schema Compositions use. Only one
 version can be `referenceable`. 
 
 {{< hint "note" >}}
-Changing which version is `referenceable:true` requires [updating the `compositeTypeRef.apiVersion`]({{<ref "./compositions#enable-composite-resources" >}}) 
+Changing which version is `referenceable:true` requires [updating the `compositeTypeRef.apiVersion`]({{<ref "./compositions#match-composite-resources" >}}) 
 of any Compositions referencing that XRD.
 {{< /hint >}}
 
diff --git a/content/v2.0-preview/composition/composite-resources.md b/content/v2.0-preview/composition/composite-resources.md
index 6ea2bb18..a849b8c8 100644
--- a/content/v2.0-preview/composition/composite-resources.md
+++ b/content/v2.0-preview/composition/composite-resources.md
@@ -115,7 +115,7 @@ Select a specific Composition for a composite resource to use with
 {{<hint "important">}}
 The selected Composition must allow the composite resource to use it with a
 `compositeTypeRef`. Read more about the `compositeTypeRef` field in the
-[Enable Composite Resources]({{<ref "./compositions#enable-composite-resources">}})
+[Enable Composite Resources]({{<ref "./compositions#match-composite-resources">}})
 section of the Composition documentation. 
 {{< /hint >}}
 
diff --git a/content/v2.0-preview/composition/compositions.md b/content/v2.0-preview/composition/compositions.md
index 31981439..a0434294 100644
--- a/content/v2.0-preview/composition/compositions.md
+++ b/content/v2.0-preview/composition/compositions.md
@@ -68,7 +68,7 @@ Crossplane has four core components that users commonly mix up:
 Creating a Composition consists of:
 * [Using composition functions](#use-a-function-in-a-composition) to define the
   resources to create.
-* [Enabling composite resources](#enable-composite-resources) to use the
+* [Enabling composite resources](#match-composite-resources) to use the
   Composition template.
 
 A Composition is a pipeline of composition functions.
diff --git a/content/v2.0-preview/guides/function-patch-and-transform.md b/content/v2.0-preview/guides/function-patch-and-transform.md
index 967e2864..2340482b 100644
--- a/content/v2.0-preview/guides/function-patch-and-transform.md
+++ b/content/v2.0-preview/guides/function-patch-and-transform.md
@@ -1835,7 +1835,7 @@ By default an XRD writes all secret keys listed in the composed resources
 
 
 For more information on connection secrets read about
-[managed resources]({{<ref "../managed-resources/managed-resources#writeConnectionSecretToRef">}}).
+[managed resources]({{<ref "../managed-resources/managed-resources">}}).
 {{</hint>}}
 
 ## Resource readiness checks