Some more fixes

Author: dunglas

core/filters.md

@@ -1,18 +1,19 @@
 # Filters
 
 API Platform Core provides a generic system to apply filters on collections. Useful filters for the Doctrine ORM are provided
-with the bundle. However the filter system is extensible enough to let you create custom filters that would fit your specific
-needs and for any data provider.
+with the library. You can also create custom filters that would fit your specific needs.
+You can also add filtering support to your custom [data providers](data-providers.md) by implementing interfaces provided
+by the library.
 
 By default, all filters are disabled. They must be enabled explicitly.
 
-When a filter is enabled, it is automatically documented as a `hydra:search` property in the collection response. It also automatically
-appears in the [NelmioApiDoc documentation](nelmio-api-doc.md) if it is available.
+When a filter is enabled, it is automatically documented as a `hydra:search` property in the collection response. It also
+automatically appears in the [NelmioApiDoc documentation](nelmio-api-doc.md) if it is available.
 
 ## Search filter
 
 If Doctrine ORM support is enabled, adding filters is as easy as registering a filter service in your `app/config/services.yml`
-file and adding an attribute to your resourcegi configuration.
+file and adding an attribute to your resource configuration.
 
 The search filter supports `exact`, `partial`, `start`, `end`, and `word_start` matching strategies:
 
@@ -231,7 +232,7 @@ class Offer
 
 Given that the collection endpoint is `/offers`, you can filter offers by boolean  with the following query: `/offers?isAvailableGenericallyInMyCountry=true`.
 
-It will return all offers with `isAvailableGenericallyInMyCountry` equals `true`.
+It will return all offers where `isAvailableGenericallyInMyCountry` equals `true`.
 
 ## Numeric Filter 
 
@@ -309,9 +310,9 @@ or order offers by the product's release date: `http://localhost:8000/api/offers
 
 ## Enabling a filter for all properties of a resource
 
-As we have seen in previous examples, properties where filters can be applied must be explicitly declared. But if you don't
-care about security and performance (e.g. an API with restricted access), it is also possible to enable built-in filters for
-all properties:
+As we have seen in previous examples, properties where filters can be applied must be explicitly declared. If you don't
+care about security and performance (e.g. an API with restricted access), it is also possible to enable built-in filters
+for all properties:
 
 ```yaml
 # app/config/services.yml