diff --git a/code-builder-home/modules/ROOT/pages/_partials/acb-reusable-steps.adoc b/code-builder-home/modules/ROOT/pages/_partials/acb-reusable-steps.adoc
index ff6c5776c..34c6782d8 100644
--- a/code-builder-home/modules/ROOT/pages/_partials/acb-reusable-steps.adoc
+++ b/code-builder-home/modules/ROOT/pages/_partials/acb-reusable-steps.adoc
@@ -271,7 +271,7 @@ Anypoint Code Builder supports scaffolding these schema fragment files if they'r
 | *AsyncAPI* | Yes | Yes | No 
 | *GraphQL* | No | No | Yes 
 | *OData* | No | No | Yes 
-| *REST* | No | No | Yes 
+| *REST* | No | Yes | Yes 
 | *SOAP* | No | No | Yes 
 |===
 
diff --git a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc
index cbd258b0a..f8fcb1317 100644
--- a/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc
+++ b/code-builder-home/modules/ROOT/pages/des-create-api-fragments.adoc
@@ -7,8 +7,6 @@ include::reuse::partial$beta-banner.adoc[tag="anypoint-code-builder"]
 //LOGO (web, desktop, or both)
 // include::partial$acb-ide-logos.adoc[tags="both-ides"]
 
-// TODO: How does this work in OAS?
-
 Using Anypoint Code Builder, you can create your own API fragments and publish them to Anypoint Exchange to share with other people,
 add fragments from Exchange to your API specification,
 or create fragments in your project to add directly to your API specification.
@@ -185,6 +183,8 @@ To add an API spec fragment to a spec:
 ** RAML specs: Use the `!include` directive.
 --
 +
+For OAS 3.0 APIs, scaffolding supports `$ref` API fragments from Exchange, including fragments with transitive dependencies, for any Mule runtime version. DataSense resolves types defined in fragment files when you scaffold into a Mule project that uses a supported Mule runtime version (currently Mule 4.9.19 and Mule 4.11.6).
++
 [tabs]
 ====
 OAS Example::