Update datamodel-providers.asciidoc (#10664)

diff --git a/documentation/datamodel/datamodel-providers.asciidoc b/documentation/datamodel/datamodel-providers.asciidoc
index dd10782b1eb293b1c79ab10817a07ec5e94c51c7..9b3c4dadd0b9a1d7693ff462f2ec8365158955ec 100644 (file)
--- a/documentation/datamodel/datamodel-providers.asciidoc
+++ b/documentation/datamodel/datamodel-providers.asciidoc
@@ -10,8 +10,8 @@ layout: page
 A common pattern in applications is that the user is first presented with a list of items, from which she selects one or several items to continue working with.
 These items could be inventory records to survey, messages to respond to or blog drafts to edit or publish.
 
-A [interfacename]#Listing# is a component that displays one or several properties from a list of item, allowing the user to inspect the data, mark items as selected and in some cases even edit the item directly through the component.
-While each listing component has it's own API for configuring exactly how the data is represented and how it can be manipulated, they all share the same mechanisms for receiving data to show.
+A [interfacename]#Listing# is a component that displays one or several properties from a list of items, allowing the user to inspect the data, mark items as selected and in some cases even edit the item directly through the component.
+While each listing component has its own API for configuring exactly how the data is represented and how it can be manipulated, they all share the same mechanisms for receiving data to show.
 
 The items are generally either loaded directly from memory or lazy loaded from some kind of backend.
 Regardless of how the items are loaded, the component is configured with one or several callbacks that define how the item should be displayed.