diff --git a/docs/src/main/sphinx/security/inspect-pem.md b/docs/src/main/sphinx/security/inspect-pem.md
index 430d55bf380e8..a5834a82338eb 100644
--- a/docs/src/main/sphinx/security/inspect-pem.md
+++ b/docs/src/main/sphinx/security/inspect-pem.md
@@ -3,20 +3,18 @@
 PEM (Privacy Enhanced Mail) is a standard for public key and certificate
 information, and an encoding standard used to transmit keys and certificates.
 
-Trino supports PEM-encoded certificates. If you want to use other supported
-formats, see:
+Trino supports PEM files. If you want to use other supported formats, see:
 
 - {doc}`JKS keystores </security/inspect-jks>`
 - {ref}`PKCS 12 <glossPKCS12>` stores. (Look up alternate commands for these in
   `openssl` references.)
 
-A single PEM-encoded file can contain either certificate or key pair
-information, or both in the same file. Certified keys can contain a chain of
-certificates from successive certificate authorities.
+A single PEM file can contain either certificate or key pair information, or
+both in the same file. Certified keys can contain a chain of certificates from
+successive certificate authorities.
 
-Follow the steps in this topic to inspect and validate PEM-encoded key and
-certificate files. See {ref}`troubleshooting-keystore` to validate JKS
-keystores.
+Follow the steps in this topic to inspect and validate key and certificate in
+PEM files. See {ref}`troubleshooting-keystore` to validate JKS keystores.
 
 (inspect-pems)=
 
@@ -122,6 +120,5 @@ characteristics:
   `DNS:clustercoord.example.com`. Certificates without SANs are not
   supported.
 
-If your PEM certificate shows valid information for your cluster, proceed to
-configure the server, as described in {ref}`cert-placement` and
-{ref}`configure-https`.
+If your PEM file shows valid information for your cluster, proceed to configure
+the server, as described in {ref}`cert-placement` and {ref}`configure-https`.