From ad8aa0df18e1581edeb42f0ec1587927abc0984b Mon Sep 17 00:00:00 2001
From: Esha Noronha <enm@umbraco.dk>
Date: Fri, 28 Mar 2025 11:59:43 +0100
Subject: [PATCH] Updated using statements as per feedback

---
 .../developer/extending/excluding-a-built-in-field.md          | 3 ++-
 .../developer/extending/excluding-a-built-in-field.md          | 3 ++-
 .../developer/extending/excluding-a-built-in-field.md          | 3 ++-
 .../developer/extending/excluding-a-built-in-field.md          | 3 ++-
 4 files changed, 8 insertions(+), 4 deletions(-)

diff --git a/10/umbraco-forms/developer/extending/excluding-a-built-in-field.md b/10/umbraco-forms/developer/extending/excluding-a-built-in-field.md
index 127179b7aa8..9714474a3e0 100644
--- a/10/umbraco-forms/developer/extending/excluding-a-built-in-field.md
+++ b/10/umbraco-forms/developer/extending/excluding-a-built-in-field.md
@@ -8,7 +8,8 @@ There might some use cases where you have no use for file upload and don't want
 The following class shows how to exclude built-in field types using a custom composer. The `Password`, `Recaptcha2` and `RichText` field types (or "answers") will no longer be available for selection when creating a form in the backoffice.
 
 ```csharp
-using Umbraco.Forms.Core.Providers;
+using Umbraco.Cms.Core.Composing;
+using Umbraco.Forms.Core.Providers.Extensions;
 using Umbraco.Forms.Core.Providers.FieldTypes;
 
 namespace MyNamespace
diff --git a/13/umbraco-forms/developer/extending/excluding-a-built-in-field.md b/13/umbraco-forms/developer/extending/excluding-a-built-in-field.md
index 127179b7aa8..9714474a3e0 100644
--- a/13/umbraco-forms/developer/extending/excluding-a-built-in-field.md
+++ b/13/umbraco-forms/developer/extending/excluding-a-built-in-field.md
@@ -8,7 +8,8 @@ There might some use cases where you have no use for file upload and don't want
 The following class shows how to exclude built-in field types using a custom composer. The `Password`, `Recaptcha2` and `RichText` field types (or "answers") will no longer be available for selection when creating a form in the backoffice.
 
 ```csharp
-using Umbraco.Forms.Core.Providers;
+using Umbraco.Cms.Core.Composing;
+using Umbraco.Forms.Core.Providers.Extensions;
 using Umbraco.Forms.Core.Providers.FieldTypes;
 
 namespace MyNamespace
diff --git a/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md b/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md
index 127179b7aa8..9714474a3e0 100644
--- a/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md
+++ b/14/umbraco-forms/developer/extending/excluding-a-built-in-field.md
@@ -8,7 +8,8 @@ There might some use cases where you have no use for file upload and don't want
 The following class shows how to exclude built-in field types using a custom composer. The `Password`, `Recaptcha2` and `RichText` field types (or "answers") will no longer be available for selection when creating a form in the backoffice.
 
 ```csharp
-using Umbraco.Forms.Core.Providers;
+using Umbraco.Cms.Core.Composing;
+using Umbraco.Forms.Core.Providers.Extensions;
 using Umbraco.Forms.Core.Providers.FieldTypes;
 
 namespace MyNamespace
diff --git a/15/umbraco-forms/developer/extending/excluding-a-built-in-field.md b/15/umbraco-forms/developer/extending/excluding-a-built-in-field.md
index 127179b7aa8..9714474a3e0 100644
--- a/15/umbraco-forms/developer/extending/excluding-a-built-in-field.md
+++ b/15/umbraco-forms/developer/extending/excluding-a-built-in-field.md
@@ -8,7 +8,8 @@ There might some use cases where you have no use for file upload and don't want
 The following class shows how to exclude built-in field types using a custom composer. The `Password`, `Recaptcha2` and `RichText` field types (or "answers") will no longer be available for selection when creating a form in the backoffice.
 
 ```csharp
-using Umbraco.Forms.Core.Providers;
+using Umbraco.Cms.Core.Composing;
+using Umbraco.Forms.Core.Providers.Extensions;
 using Umbraco.Forms.Core.Providers.FieldTypes;
 
 namespace MyNamespace