English translation corr.

gui/admin-gui/src/main/resources/localization/Midpoint.properties

@@ -2548,8 +2548,8 @@ ResourceWizard.expression.tooltip.expression=The XML representation of the expre
 ResourceWizard.expression.tooltip.language=Programming language in which is the expression script written.
 ResourceWizard.expression.tooltip.policyRef=Reference to a value policy object. The specified value policy will be used as a template to generate a value.
 ResourceWizard.expression.tooltip.type=The type of expression. This specifies whether the expression is a script, value generator or something else.
-ResourceWizard.help.capabilityStep=<p>Resource <i>capabilities</i> are the things that the resource can do. Not all the resource are equal in their capabilities. E.g. one resource supports account activation (enabling and disabling accounts) but other does not. One resource provides read-write access while other can support read-only access. One resource supports real-time synchronization while other does not. The <i>capabilities</i> define what features the resource supports so system can behave accordingly.</p><p>All the capabilities can be <i>disabled</i> (i.e. turned off). Disabling the capability will cause that system will not use that part of the connector and resource. The capabilities are usually disabled if they are faulty. E.g. if there is a bug in a connector or on the resource then the bug might be circumvented if appropriate capability is disabled. But the capabilities may be disabled also for administrative reasons. E.g. disabling <tt>Create</tt>, <tt>Update</tt> and <tt>Delete</tt> capabilities makes the resource efficiently read-only.</p><p>Some capabilities can be <i>simulated</i>. It means that system can pretend that the resource has specific capability even though it does not have it. E.g. an <i>activation</i> capability can be simulated by setting a specific account attribute to a specific value to disable an account. Such simulated capabilities usually require some configuration. This can also be configured on this page.</p><p>See <a href="https://wiki.evolveum.com/display/midPoint/Resource+Capabilities">Resource Capabilities wiki page</a> for more details.
-ResourceWizard.help.configurationStep=<p>This stage of the wizard configures connector configuration properties. They usually define network parameters used to access the resource such as hostname and port numbers. Additional connection parameters such as operation network timeouts and connection pooling configuration can be specified here.</p><p>There connector configuration properties are unique for each connector. The specific set of configuration properties are determined by connector configuration schema. Therefore the content of this page depends on the connector type that was selected in the previous page.</p>
+ResourceWizard.help.capabilityStep=<p>Resource <i>capabilities</i> are the things that the resource can do. Not all the resource are equal in their capabilities. E.g. one resource supports account activation (enabling and disabling accounts) but other does not. One resource provides read-write access while other can support read-only access. One resource supports real-time synchronization while other does not. The <i>capabilities</i> define what features the resource supports so system can behave accordingly.</p><p>All the capabilities can be <i>disabled</i> (i.e. turned off). Disabling the capability will cause that system will not use that part of the connector and resource. The capabilities are usually disabled if they are faulty. E.g. if there is a bug in a connector or on the resource then the bug might be circumvented if appropriate capability is disabled. But the capabilities may be disabled also for administrative reasons. E.g. disabling <tt>Create</tt>, <tt>Update</tt> and <tt>Delete</tt> capabilities makes the resource efficiently read-only.</p><p>Some capabilities can be <i>simulated</i>. It means that system can pretend that the resource has specific capability even though it does not have it. E.g. an <i>activation</i> capability can be simulated by setting a specific account attribute to a specific value to disable an account. Such simulated capabilities usually require some configuration. This can also be configured on this page.</p><p>See <a href="https://wiki.evolveum.com/display/midPoint/Resource+Capabilities">Resource Capabilities wiki page</a> for more details.</p>
+ResourceWizard.help.configurationStep=<p>This stage of the wizard configures connector configuration properties. They usually define network parameters used to access the resource such as hostname and port numbers. Additional connection parameters such as operation network timeouts and connection pooling configuration can be specified here.</p><p>The connector configuration properties are unique for each connector. The specific set of configuration properties are determined by connector configuration schema. Therefore the content of this page depends on the connector type that was selected in the previous page.</p>
 ResourceWizard.help.nameStep=<p>This stage of the wizard configures basic properties of the resource. It can be used to configure resource name and description. Connector name is mandatory and must be unique. Connector that will be used to access the resource must also be configured. Connectors are deployed on connector hosts. If the connector host is left empty then connectors deployed directly in the system instance will be used.</p><p>See <a href="https://wiki.evolveum.com/display/midPoint/Resource+Configuration">Resource Configuration wiki page</a> for detailed explanation of resource configuration.</p>
 ResourceWizard.help.schemaHandlingStep=<p>This step is used to provide <b>configuration</b> for handling of resource schema. The configuration displayed on this page tells system <b>what to do</b> with resource object classes and attributes. It contains the configuration of mappings between user properties and account attributes, configuration of account types, groups, provisioning dependencies, password mapping and so on.</p><p>The configuration is grouped into <b>object types</b>. Each object type defines the behavior for specific account type, entitlement type, OU, etc. The object type is uniquely identified by the combination of <i>kind</i> and <i>intent</i>. The <i>kind</i> defines what kind of the object it is:<ul><li>kind=<tt>account</tt> means that the object is an account, i.e. that it represents a user.</li><li>kind=<tt>entitlement</tt> is applied to groups, roles, privileges, ACIs and similar objects that can be associated with accounts and which give privileges or access rights to the account.</li><li>kind=<tt>generic</tt> applies to other objects such as organizational units (OUs), domains, etc.</li></ul>Intent is a plain string that can be used to distinguish several object types. E.g. it can be used to define several account types, e.g. "default user account", "administration account", "testing account" and so on. See <a href="https://wiki.evolveum.com/display/midPoint/Kind%2C+Intent+and+ObjectClass">Kind, Intent and ObjectClass wiki page</a> for more details.</p><p>More details about schema handling configuration are provided on <a href="https://wiki.evolveum.com/display/midPoint/Resource+Schema+Handling">Resource Schema Handling wiki page</a>.
 ResourceWizard.help.schemaStep=<p>This page shows resource schema. The resource schema defines <i>object classes</i> that the connector can manage, e.g. accounts, groups, organizational units and so on. The schema defines a set of <i>attributes</i> for each object class. The schema is presented here in read-only form so you can inspect it and familiarize yourself with the data model that the resource provides.</p><p>The resource schema presented at this page is usually retrieved from the resource and automatically generated by system. Resource schema defines what the resource <b>can do</b>, i.e. what object classes it defines and what attributes are used in the object classes. Therefore the schema is read-only. It is <b>not</b> a configuration. It does <b>not</b> defines how system uses the object classes and attributes. That is configured in next steps of the wizard.</p><p>See <a href="https://wiki.evolveum.com/display/midPoint/Resource+Schema">Resource Schema wiki page</a> for detailed explanation of resource schema concepts</p>