diff --git a/docs/book/v3/application-integration/providing-filters-via-modules.md b/docs/book/v3/application-integration/providing-filters-via-modules.md
index d290f54a..f21ce109 100644
--- a/docs/book/v3/application-integration/providing-filters-via-modules.md
+++ b/docs/book/v3/application-integration/providing-filters-via-modules.md
@@ -1,6 +1,6 @@
# Providing Filters via Modules
-If you wish to indicate that your laminas-mvc module provides filters, have your `Module` class implement `Laminas\Filter\FilterProviderInterface`, which defines the method:
+If you wish to indicate that your laminas-mvc module provides filters, have your `Module` class implement `Laminas\ModuleManager\Feature\FilterProviderInterface`, which defines the method:
```php
/**
@@ -11,6 +11,8 @@ public function getFilterConfig();
The method should return an array of configuration following the [laminas-servicemanager configuration format](https://docs.laminas.dev/laminas-servicemanager/configuring-the-service-manager/).
+Further information can be found in the [Module Manager documentation](https://docs.laminas.dev/laminas-modulemanager/module-manager/#servicelistener).
+
If you are not using laminas-mvc, but are using a dependency injection container (e.g., if you are using Mezzio), you can also provide filters using the top-level `filters` configuration key; the value of that key should be laminas-servicemanager configuration, as linked above.
(laminas-mvc users may also provide configuration in the same way, and omit implementation of the `FilterProviderInterface`.)
diff --git a/docs/book/v3/migration/v2-to-v3.md b/docs/book/v3/migration/v2-to-v3.md
index f387777c..2e91465d 100644
--- a/docs/book/v3/migration/v2-to-v3.md
+++ b/docs/book/v3/migration/v2-to-v3.md
@@ -343,3 +343,8 @@ Various filters such as `StringToLower` and `StringToUpper` inherited from the a
This class has been removed and the affected filters no longer inherit from anything.
In order to provide consistent handling of the `encoding` option that has been re-implemented in these filters, a new class `EncodingOption` has been introduced which provides static methods to validate a given encoding option.
This change is unlikely to affect you, unless you have inherited from this class. In which case, you will need to implement the provision of an encoding option for your custom filter and remove `AbstractUnicode` from your inheritance tree.
+
+### Removal of the `FilterProviderInterface`
+
+This legacy interface is related to Laminas MVC Module Manager integration and was superseded by `Laminas\ModuleManager\Feature\FilterProviderInterface`.
+If your code still references `Laminas\Filter\FilterProviderInterface`, replace its usage with the interface [shipped by Module Manager](https://docs.laminas.dev/laminas-modulemanager/module-manager/#servicelistener).
diff --git a/psalm-baseline.xml b/psalm-baseline.xml
index 5b897219..eb3e2550 100644
--- a/psalm-baseline.xml
+++ b/psalm-baseline.xml
@@ -185,11 +185,6 @@
-
-
-
-
-
@@ -309,12 +304,6 @@
-
-
-
-
-
-
diff --git a/src/FilterProviderInterface.php b/src/FilterProviderInterface.php
deleted file mode 100644
index 72978d28..00000000
--- a/src/FilterProviderInterface.php
+++ /dev/null
@@ -1,23 +0,0 @@
- $provider->getDependencyConfig(),
];
}
-
- /**
- * Register a specification for the FilterManager with the ServiceListener.
- *
- * @param ModuleManager $moduleManager
- */
- public function init($moduleManager): void
- {
- $event = $moduleManager->getEvent();
- $container = $event->getParam('ServiceManager');
- $serviceListener = $container->get('ServiceListener');
-
- $serviceListener->addServiceManager(
- 'FilterManager',
- 'filters',
- FilterProviderInterface::class,
- 'getFilterConfig'
- );
- }
}