GITBOOK-582: Replace 3rd party with 'other MDM'

docs/advanced-configuration/application-settings/static-validation.md

@@ -12,9 +12,9 @@ Applicable to version 1.6 and above
 
 **Value:** _true_ or _false_
 
-**Description:** This setting helps you to request certificates from [3rd-party MDM systems](../../certificate-deployment/static-certificates/) (i.e. other than Intune and JAMF).
+**Description:** This setting helps you to request certificates from [Other MDM systems](../../certificate-deployment/static-certificates/) (i.e. other than Intune and JAMF).
 
-**True**: SCEPman listens at the additional SCEP server endpoint with the path `/static`. Use in conjunction with AppConfig:StaticValidation:RequestPassword. **False** (default): SCEPman does not issue certificates for 3rd-party MDM systems (i.e. other than Intune and JAMF).
+**True**: SCEPman listens at the additional SCEP server endpoint with the path `/static`. Use in conjunction with AppConfig:StaticValidation:RequestPassword. **False** (default): SCEPman does not issue certificates for Other MDM systems (i.e. other than Intune and JAMF).
 
 ## AppConfig:StaticValidation:DefaultEkus
 
@@ -44,7 +44,7 @@ Applicable to version 1.6 and above
 
 **Value:** _String_
 
-**Description:** A challenge password that a 3rd-party MDM system must include in every SCEP request to acquire a certificate. Only used if AppConfig:StaticValidation:Enabled is set to _true_.
+**Description:** A challenge password that Other MDM system must include in every SCEP request to acquire a certificate. Only used if AppConfig:StaticValidation:Enabled is set to _true_.
 
 We recommend to define this setting as Secret in Azure Key Vault. The Secret must have the name _AppConfig--StaticValidation--RequestPassword_.
 

docs/certificate-deployment/static-certificates/kandji.md

@@ -6,7 +6,7 @@ This feature requires version 1.6 or above.
 
 SCEPman can be connected to [Kandji](https://www.kandji.io/) as External CA. Via SCEPman's static interface and a challenge password enrolled devices will be able to obtain certificates.
 
-For more general information about 3rd-party MDM solutions and SCEPman integration please check [here](./).
+For more general information about other MDM solutions and SCEPman integration please check [here](./).
 
 ## Enable Kandji Integration
 

docs/certificate-deployment/static-certificates/mosyle.md

@@ -6,7 +6,7 @@ This feature requires version 1.6 or above.
 
 SCEPman can be connected to [Mosyle](https://mosyle.com/) as External CA. Via SCEPman's static interface and a challenge password enrolled devices will be able to obtain certificates.
 
-For more general information about 3rd-party MDM solutions and SCEPman integration please check [here](./).
+For more general information about other MDM solutions and SCEPman integration please check [here](./).
 
 ## Enable Mosyle Integration
 

docs/certificate-deployment/static-certificates/soti-mobicontrol.md

@@ -2,7 +2,7 @@
 
 SCEPman can be integrated with SOTI MobiControl as a Certificate Authority. By connecting both systems through SCEPman's Static SCEP interface, MobiControl-enrolled devices can obtain device certificates from SCEPman.
 
-For more general information about 3rd-party MDM solutions and SCEPman integration please check [here](./).
+For more general information about other MDM solutions and SCEPman integration please check [here](./).
 
 ## Enable SOTI MobiControl Integration
 

docs/details.md

@@ -45,7 +45,7 @@ SCEPman creates the CA root certificate during the initial installation. However
 
 #### Certificate Master
 
-Certificate Master allows [Enterprise Edition](editions.md#edition-comparison) customers to (manually) issue certificates in scenarios where an automatic enrollment via SCEP / MDM is not possible. Common examples are the issuance of [TLS server certificates](certificate-deployment/certificate-master/tls-server-certificate-pkcs-12.md) or user certificates for [smart cards / YubiKeys](certificate-deployment/certificate-master/user-certificate.md). Furthermore, with Certificate Master, administrators can [manage](certificate-deployment/manage-certificates.md) any certificate issued by SCEPman, whether they were automatically enrolled through SCEP via Intune, Jamf, 3rd party MDMs, EST, the [Enrollment REST API](certificate-deployment/api-certificates.md) or manually via Certificate Master UI itself.
+Certificate Master allows [Enterprise Edition](editions.md#edition-comparison) customers to (manually) issue certificates in scenarios where an automatic enrollment via SCEP / MDM is not possible. Common examples are the issuance of [TLS server certificates](certificate-deployment/certificate-master/tls-server-certificate-pkcs-12.md) or user certificates for [smart cards / YubiKeys](certificate-deployment/certificate-master/user-certificate.md). Furthermore, with Certificate Master, administrators can [manage](certificate-deployment/manage-certificates.md) any certificate issued by SCEPman, whether they were automatically enrolled through SCEP via Intune, Jamf and other MDMs, EST, the [Enrollment REST API](certificate-deployment/api-certificates.md) or manually via Certificate Master UI itself.
 
 {% content-ref url="certificate-deployment/certificate-master/" %}
 [certificate-master](certificate-deployment/certificate-master/)

docs/other/faqs/security-faq.md

@@ -110,7 +110,7 @@ SCEPman leverages Managed Identities to implement a secure permission model in y
 
 1. SCEP-endpoint(s)
    * Invoked for SCEP-requests.
-   * Based on the configuration, SCEPman may expose several SCEP-endpoints for Intune, Jamf Pro, DCs, generic 3rd-party MDMs.
+   * Based on the configuration, SCEPman may expose several SCEP-endpoints for Intune, Jamf Pro, DCs, generic Other MDMs.
 2. Enrollment REST API
    * Allows Certificate Master to request certificates from SCEPman's core service.
    * Allows custom applications to request certificates from SCEPman's core service.