diff --git a/docs/guide/ad/dirsync.md b/docs/guide/ad/dirsync.md index 4d52f0f78..90a1f97e1 100644 --- a/docs/guide/ad/dirsync.md +++ b/docs/guide/ad/dirsync.md @@ -6,7 +6,7 @@ redirect_from: "/docs/guide/ad/dirsync/" # Directory Synchronization (DirSync) -Active Directory provides it's own control for tracking changes in the directory. Note the following constraints when configuring your search: +Active Directory provides its own control for tracking changes in the directory. Note the following constraints when configuring your search: baseDN | must be the root of a directory partition, which can be a domain partition, the configuration partition, or the schema partition scope | must be the entire subtree of the partition diff --git a/docs/guide/operations.md b/docs/guide/operations.md index 89c7706e4..ed41bcd21 100644 --- a/docs/guide/operations.md +++ b/docs/guide/operations.md @@ -31,7 +31,7 @@ public interface Operation ### Synchronous calls -Ldaptive is asynchronous at it's core but provides an *execute* to wait for operations to complete. +Ldaptive is asynchronous at its core but provides an *execute* to wait for operations to complete. {% highlight java %} {% include source/operations/1.java %} diff --git a/docs/guide/operations/search/async.md b/docs/guide/operations/search/async.md index cd1cbb4c0..5cd585880 100644 --- a/docs/guide/operations/search/async.md +++ b/docs/guide/operations/search/async.md @@ -8,7 +8,7 @@ redirect_from: "/docs/guide/operations/search/async/" # Asynchronous Searching -Ldaptive is asynchronous at it's core since it is built on Netty. The `#execute` method blocks until a result is received, however it's possible to configure handlers to process results as they arrive. +Ldaptive is asynchronous at its core since it is built on Netty. The `#execute` method blocks until a result is received, however it's possible to configure handlers to process results as they arrive. {% highlight java %} {% include source/operations/search/async/1.java %} diff --git a/docs/guide/properties.md b/docs/guide/properties.md index d4e72ea88..bf8640880 100644 --- a/docs/guide/properties.md +++ b/docs/guide/properties.md @@ -6,7 +6,7 @@ redirect_from: "/docs/guide/properties/" # Properties -In order to support various configuration formats Ldaptive provides the ability to configure it's objects with Properties. Each property identifies a method which is reflectively invoked with the value. +In order to support various configuration formats Ldaptive provides the ability to configure its objects with Properties. Each property identifies a method which is reflectively invoked with the value. {% highlight text %} org.ldaptive.ldapUrl=ldap://directory.ldaptive.org diff --git a/v1/docs/guide/ad/dirsync.md b/v1/docs/guide/ad/dirsync.md index 2d6d7b6b7..6b98d2e76 100644 --- a/v1/docs/guide/ad/dirsync.md +++ b/v1/docs/guide/ad/dirsync.md @@ -6,7 +6,7 @@ redirect_from: "/v1/docs/guide/ad/dirsync/" # Directory Synchronization (DirSync) -Active Directory provides it's own control for tracking changes in the directory. Note the following constraints when configuring your search: +Active Directory provides its own control for tracking changes in the directory. Note the following constraints when configuring your search: baseDN | must be the root of a directory partition, which can be a domain partition, the configuration partition, or the schema partition scope | must be the entire subtree of the partition diff --git a/v1/docs/guide/connections.md b/v1/docs/guide/connections.md index 73e14cd46..9722b4b46 100644 --- a/v1/docs/guide/connections.md +++ b/v1/docs/guide/connections.md @@ -106,7 +106,7 @@ Supported private key formats include: - hostname must match the first CN - if certificate begins with a wildcard, domains are used for matching -As of version 1.2.3, hostname validation can be controlled via the `CertificateHostnameVerifier` interface which is a property of `SslConfig`. One important caveat is that the JNDI provider *always* performs it's own hostname check when using startTLS. Any custom hostname checks will only be performed if their check fails. +As of version 1.2.3, hostname validation can be controlled via the `CertificateHostnameVerifier` interface which is a property of `SslConfig`. One important caveat is that the JNDI provider *always* performs its own hostname check when using startTLS. Any custom hostname checks will only be performed if their check fails. ## Operation Retry diff --git a/v1/docs/guide/properties.md b/v1/docs/guide/properties.md index 468e3d4de..3aec6eb69 100644 --- a/v1/docs/guide/properties.md +++ b/v1/docs/guide/properties.md @@ -6,7 +6,7 @@ redirect_from: "/v1/docs/guide/properties/" # Properties -In order to support various configuration formats Ldaptive provides the ability to configure it's objects with Properties. Each property identifies a method which is reflectively invoked with the value. +In order to support various configuration formats Ldaptive provides the ability to configure its objects with Properties. Each property identifies a method which is reflectively invoked with the value. {% highlight text %} org.ldaptive.ldapUrl=ldap://directory.ldaptive.org diff --git a/v1/docs/guide/providers.md b/v1/docs/guide/providers.md index f301c5ef1..9655a3c38 100644 --- a/v1/docs/guide/providers.md +++ b/v1/docs/guide/providers.md @@ -32,7 +32,7 @@ or it can be specified with a JVM system property: ## Installation & Configuration -Providers may have custom properties that aren't represented in the ldaptive configuration objects. Those properties are detailed in the following sections. If you don't like the behavior of a provider consider extending it to change it's functionality. +Providers may have custom properties that aren't represented in the ldaptive configuration objects. Those properties are detailed in the following sections. If you don't like the behavior of a provider consider extending it to change its functionality. ### JNDI Provider diff --git a/v1/docs/guide/templates.md b/v1/docs/guide/templates.md index 37a02c450..064ae7a3b 100644 --- a/v1/docs/guide/templates.md +++ b/v1/docs/guide/templates.md @@ -224,7 +224,7 @@ Expects to find /templates-context.xml in the classpath and returns search resul {% endhighlight %} -This webapp can be used with the maven war overlay to customize it's configuration: +This webapp can be used with the maven war overlay to customize its configuration: {% highlight xml %}