Fixing typos

topics/getting-started/hello-world.adoc

@@ -351,3 +351,5 @@ The RPT provides everything you need to enforce authorization decisions at the r
 * Checking if a request sent to the resource server trying to access a protected resource matches any permissions within the RPT
 
 You can even use the information within a RPT to protect resources within a page like buttons or any other visual component.
+
+Another way to validate a RPT and obtain the granted permissions is using the link:../service/protection/token-introspection.html[Token Introspection Endpoint].

topics/permission/create-resource.adoc

@@ -1,8 +1,8 @@
 == Creating Resource-based Permissions
 
-A Resource-based permissions defines a set of one or more resources to protect using a set of one or more authorization policies.
+A Resource-based permissionsdefines a set of one or more resources to protect using a set of one or more authorization policies.
 
-To create a new permission select the option *Resource-based* in the dropdown located in the right upper corner of the permission listing. In {{book.project.name}}, a resource-based permissions consist of the following information:
+To create a new permission select the option *Resource-based* in the dropdown located in the right upper corner of the permission listing. In {{book.project.name}}, a resource-based permission consists of the following information:
 
 * *Name*
 +

topics/permission/create-scope.adoc

@@ -1,10 +1,10 @@
 == Creating Resource-based Permissions
 
-A Scope-based permissions defines a set of one or more scopes to protect using a set of one or more authorization policies. Unlike the resource-based permissions, this permission type
-allows you to create permissions not only for the resource, but also for the scopes associated with it, providing you more granularity when defining the permissions that rule your resources and the
+A Scope-based permission defines a set of one or more scopes to protect using a set of one or more authorization policies. Unlike the resource-based permissions, this permission type
+allows you to create permissions not only for a resource, but also for the scopes associated with it, providing more granularity when defining the permissions that rule your resources and the
 actions that can be performed on them.
 
-To create a new permission select the option *Scope-based* in the dropdown located in the right upper corner of the permission listing. In {{book.project.name}}, a scope-based permissions consist of the following information:
+To create a new permission select the option *Scope-based* in the dropdown located in the right upper corner of the permission listing. In {{book.project.name}}, a scope-based permission consists of the following information:
 
 * *Name*
 +

topics/policy/drools-policy.adoc

@@ -1,7 +1,7 @@
 == Drools-Based Policy
 
-This type of policy allows you to define conditions for your permissions using Drools Rules. It is one of the _Rule-Based_ policy types
-supported by {{book.project.name}}, giving to you a lot of flexibility to write any policy based on the link::/policy/evaluation-api.adoc[Evaluation API].
+This type of policy allows you to define conditions for your permissions using Drools. It is one of the _Rule-Based_ policy types
+supported by {{book.project.name}}, providing a lot of flexibility to write any policy based on the link::/policy/evaluation-api.adoc[Evaluation API].
 
 === Configuration
 

topics/policy/js-policy.adoc

@@ -1,7 +1,7 @@
 == JavaScript-Based Policy
 
 This type of policy allows you to define conditions for your permissions using JavaScript. It is one of the _Rule-Based_ policy types
-supported by {{book.project.name}}, giving to you a lot of flexibility to write any policy based on the link::/policy/evaluation-api.adoc[Evaluation API].
+supported by {{book.project.name}}, providing lot of flexibility to write any policy based on the link::/policy/evaluation-api.adoc[Evaluation API].
 
 === Configuration