Skip to content
This repository was archived by the owner on Feb 28, 2023. It is now read-only.

Commit d0e2386

Browse files
authored
Fix spelling.
Signed-off-by: Bastian Fredriksson <[email protected]>
1 parent 4171854 commit d0e2386

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

roles/operations_manual/files/chapters/operations.rst.j2

+1-1
Original file line numberDiff line numberDiff line change
@@ -183,7 +183,7 @@ In a Microsoft environment, you can renew the CA certificate with a new CA certi
183183

184184
If you renew a CA certificate on a standalone CA machine, you need to manually publish it to Active Directory. Windows devices connected to the domain will obtain the new CA certificate automatically when they restart or after the Group Policy Refresh Interval (8 hours by default).
185185

186-
Clients can use the propritary Microsoft certificate extension ``1.3.6.1.4.1.311.21.2`` to link the new CA certificate to the old CA certificate.
186+
Clients can use the proprietary Microsoft certificate extension ``1.3.6.1.4.1.311.21.2`` to link the new CA certificate to the old CA certificate.
187187

188188
In a non-Microsoft environment it is recommended to create a new CA with a new keypair and subject DN and reissue any active certificates. If you are creating a new root CA you may have to manually distribute the new root CA certificate to the truststore of any machines which require it.
189189

0 commit comments

Comments
 (0)