diff --git a/plugins/modules/acme_certificate.py b/plugins/modules/acme_certificate.py
index 107a1450..e8dd0af2 100644
--- a/plugins/modules/acme_certificate.py
+++ b/plugins/modules/acme_certificate.py
@@ -62,9 +62,9 @@ seealso:
     description: Helps preparing C(tls-alpn-01) challenges.
   - module: community.crypto.openssl_privatekey
     description: Can be used to create private keys (both for certificates and accounts).
-  - module: commuinty.crypto.openssl_csr
+  - module: community.crypto.openssl_csr
     description: Can be used to create a Certificate Signing Request (CSR).
-  - module: comunity.crypto.certificate_complete_chain
+  - module: community.crypto.certificate_complete_chain
     description: Allows to find the root certificate for the returned fullchain.
   - module: community.crypto.acme_certificate_revoke
     description: Allows to revoke certificates.
diff --git a/plugins/modules/x509_certificate.py b/plugins/modules/x509_certificate.py
index f974d29a..b27ec7c4 100644
--- a/plugins/modules/x509_certificate.py
+++ b/plugins/modules/x509_certificate.py
@@ -594,7 +594,7 @@ notes:
     - All ASN.1 TIME values should be specified following the YYYYMMDDHHMMSSZ pattern.
     - Date specified should be UTC. Minutes and seconds are mandatory.
     - For security reason, when you use C(ownca) provider, you should NOT run
-      M(community.general.x509_certificate) on a target machine, but on a dedicated CA machine. It
+      M(community.crypto.x509_certificate) on a target machine, but on a dedicated CA machine. It
       is recommended not to store the CA private key on the target machine. Once signed, the
       certificate can be moved to the target machine.
 seealso: