Update realm.md.vtl
diff --git a/realm.md.vtl b/realm.md.vtl
index f22729c..a8d57e6 100644
--- a/realm.md.vtl
+++ b/realm.md.vtl
@@ -24,7 +24,7 @@
* [Role based Authorization](#Realm-RoleBasedAuthorization)
* [Permission based Authorization](#Realm-PermissionBasedAuthorization)
-A `Realm` is a component that can access application-specific security data such as users, roles, and permissions. The `Realm` translates this application-specific data into a format that Shiro understands so Shiro can in turn provide a single easy-to-understand [Subject](subject.html "Subject") programming API no matter how many data sources exist or how application-specific your data might be.
+A `Realm` is a component that can access application-specific security data such as users, roles and permissions. The `Realm` translates this application-specific data into a format that Shiro understands so Shiro can in turn provide a single easy-to-understand [Subject](subject.html "Subject") programming API no matter how many data sources exist or how application-specific your data might be.
Realms usually have a 1-to-1 correlation with a data source such as a relational database, LDAP directory, file system, or other similar resource. As such, implementations of the `Realm` interface use data source-specific APIs to discover authorization data (roles, permissions, etc), such as JDBC, File IO, Hibernate or JPA, or any other Data Access API.
