Updated some grammar etc

Author: sofietoft

15/umbraco-cms/reference/content-type-filters.md

@@ -4,27 +4,32 @@ description: Describes how to use Content Type Filters to restrict the allowed c
 
 # Filtering Allowed Content Types
 
-When creating content editors are presented with a dialog where they select the type of content they want to create. The options available are defined when setting up the document, media and member types in the _Settings_ section.
+When content editors add new content they are presented with a dialog where they must select the type of content they want to create. The options available are defined when setting up the Document, Media, and Member types in the **Settings** section.
 
-Sometimes implementors or packages have a requirement to use some additional logic to determine which options are available.
+Implementors and package creators can add additional logic to determine which options are available to the editors.
 
-This is possible using content type filters.
+This is possible using Content Type Filters.
 
 {% hint style="info" %}
-The uses cases supported here are similar to those where the `SendingAllowedChildrenNotification` would be used in Umbraco 13 or earlier.
+The use cases supported here are similar to those where the `SendingAllowedChildrenNotification` would be used in Umbraco 13 or earlier.
 {% endhint %}
 
 ## Implementing a Content Type Filter
 
-To create a content type filter you use a class that implements the `IContentTypeFilter` interface (found in the `Umbraco.Cms.Core.Services.Filters` namespace).
+To create a Content Type Filter you use a class that implements the `IContentTypeFilter` interface (found in the `Umbraco.Cms.Core.Services.Filters` namespace).
 
-There are two methods you can implement. One is for filtering the content types allowed at the content root. The other is for the content types allowed below a given parent node.
+There are two methods you can implement:
 
-If you don't want to filter for one or other method, you can return the provided collection unmodified.
+* One for filtering the content types allowed at the content root
+* One for the content types allowed below a given parent node.
+
+If you don't want to filter using one of the two approaches, you can return the provided collection unmodified.
+
+### Example Use case
 
 The following example shows a typical use case. Often websites will have a "Home Page" Document Type which is created at the root. Normally, only one of these is required. You can enforce that using the following Content Type Filter.
 
-Here we are querying the existing content available at the root. Normally we can create a "Home Page" here, but if one already exists, we remove the option:
+The code below is querying the existing content available at the root. Normally you can create a "Home Page" here, but if one already exists that option is removed:
 
 ```csharp
 internal class OneHomePageOnlyContentTypeFilter : IContentTypeFilter
@@ -57,9 +62,9 @@ internal class OneHomePageOnlyContentTypeFilter : IContentTypeFilter
 }
 ```
 
-Content Type Filters are registered as a collection, so it's possible to have more than one either in the solution or an installed package.
+Content Type Filters are registered as a collection, making it possible to have more than one in the solution or an installed package.
 
-You use a composer to register the filters:
+The filters need to be registered in a composer:
 
 ```csharp
 public class MyComposer : IComposer