many small typo fixes, mostly a/an articles, is is -> it is

docs/diag/troubleshooting/connectors.adoc

@@ -261,7 +261,7 @@ But one way or another this is the best chance to learn what the connector is do
 If that fails you have to resort to packet sniffer and similar tools.
 
 Each connector has its own logger names.
-The most reliable way to find out what it is is to look at the connector documentation or connector source code.
+The most reliable way to find out what it is to look at the connector documentation or connector source code.
 But as rule of thumb the connectors usually use logger names matching their Java package.
 This is supposed to be the same as the package prefix used in the `connectorType` property (see wiki:ConnectorType[ConnectorType]), e.g. `com.evolveum.polygon.connector.ldap`.
 

docs/diag/troubleshooting/mappings/index.adoc

@@ -622,7 +622,7 @@ But one way or another this is the best chance to learn what the connector is do
 If that fails you have to resort to packet sniffer and similar tools.
 
 Each connector has its own logger names.
-The most reliable way to find out what it is is to look at the connector documentation or connector source code.
+The most reliable way to find out what it is to look at the connector documentation or connector source code.
 But as rule of thumb the connectors usually use logger names matching their Java package.
 This is supposed to be the same as the package prefix used in the `connectorType` property (see wiki:ConnectorType[ConnectorType]), e.g. `com.evolveum.polygon.connector.ldap`.
 

docs/expressions/sequences/configuration.adoc

@@ -89,7 +89,7 @@ Sequence values are retrieved just once for each operation.
 The values are kept in wiki:Model+Context[Model Context] and re-used every time the expression is re-evaluated during that operation.
 This is a mechanism to avoid taking multiple values from the sequence.
 However, the assigned value is not explicitly remember across operations.
-Therefore is is strongly recommended to use sequences in _weak_ mappings.
+Therefore it is strongly recommended to use sequences in _weak_ mappings.
 
 The operation that retrieved a sequence value may fail before it can persistently store the object.
 In such a case midPoint will take care of returning the value back to the sequence for reclamation.

docs/resources/resource-configuration/simulated-disable.adoc

@@ -14,7 +14,7 @@ There is nothing to do for these resources except for wiki:Resource+Schema+Handl
 
 But there are also resources that do not support the activation at all.
 Or at least not directly.
-Typical case is is a resource connected by wiki:DatabaseTable+Connector[DatabaseTable connector]. The DatabaseTable connector is very generic.
+Typical case it is a resource connected by wiki:DatabaseTable+Connector[DatabaseTable connector]. The DatabaseTable connector is very generic.
 And even if the table exposed by the connector does include a status column the connector does not know about it.
 Therefore it cannot provide this capability.
 But even though the connector does not provide this capability midPoint can.

docs/roles-policies/assignment/configuration/index.adoc

@@ -509,7 +509,7 @@ Assignment, all by itself, is a great and powerful mechanism.
 But it can get even better.
 One of the main purposes of the `assignment` structure is to contain parameters, e.g. parameters that are not related to the user or a role, but parameters that are related to the association of a user to a role.
 The usual assignment parameters are start and end dates of the assignment.
-This can be used in case an role is assigned to a user only for a specified amount of time, when a new employee record is created before he really joins the company, etc.
+This can be used in case a role is assigned to a user only for a specified amount of time, when a new employee record is created before he really joins the company, etc.
 Such approach is illustrated in the following example.
 The example specifies that Jack Sparrow will be assigned to role of a Captain, but only starting 30th of May 1623 AD.
 

docs/roles-policies/assignment/index.adoc

@@ -119,7 +119,7 @@ Assignment, all by itself, is a great and powerful mechanism.
 But it can get even better.
 One of the main purposes of the `assignment` structure is to contain parameters, e.g. parameters that are not related to the user or a role, but parameters that are related to the association of a user to a role.
 The usual assignment parameters are start and end dates of the assignment.
-This can be used in case an role is assigned to a user only for a specified amount of time, when a new employee record is created before he really joins the company, etc.
+This can be used in case a role is assigned to a user only for a specified amount of time, when a new employee record is created before he really joins the company, etc.
 The assignment can also be temporarily disabled.
 This kind of assignment parameters, called wiki:Activation[activation], is pre-defined in midPoint.
 Therefore the IDM system will take care of processing that by itself, without any substantial customization.

docs/roles-policies/roles-and-policies-configuration/index.adoc

@@ -312,7 +312,7 @@ This is a very important feature that allows efficient evaluation of big role hi
 
 Marking role as idempotent is likely to result in huge performance improvements in systems with large role hierarchies.
 But there are also risks of incorrect evaluation of the roles.
-If an role is idempotent then is is also assumed that any roles included in this role are also idempotent.
+If a role is idempotent then it is also assumed that any roles included in this role are also idempotent.
 Therefore please take care when constructing role hierarchies.
 This property has a default value that indicates no idempotence.