Fix variable names in docs

aws · Jan 30, 2024 · 84c18b0 · 84c18b0
1 parent 3e0c530
commit 84c18b0
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 7 deletions.
diff --git a/documents/MQTT5_Userguide.md b/documents/MQTT5_Userguide.md
@@ -77,7 +77,7 @@ For X509 based mutual TLS, you can create a client where the certificate and pri
 
 ```python
     # X.509 based certificate file
-    cert_file_path = "<certificate file path>"
+    cert_filepath = "<certificate file path>"
     # PKCS#1 or PKCS#8 PEM encoded private key file
     pri_key_filepath = "<private key file path>"
 
@@ -86,8 +86,8 @@ For X509 based mutual TLS, you can create a client where the certificate and pri
     # Create an MQTT5 Client using mqtt5_client_builder
     client = mqtt5_client_builder.mtls_from_path(
         endpoint = "<account-specific endpoint>",
-        cert_filepath=certificate_file_path,
-        pri_key_filepath=private_key_filePath))
+        cert_filepath=cert_filepath,
+        pri_key_filepath=pri_key_filepath))
 ```
 
 #### **Direct MQTT with Custom Authentication**

diff --git a/samples/mqtt5_pubsub.md b/samples/mqtt5_pubsub.md
@@ -90,7 +90,7 @@ For X509 based mutual TLS, you can create a client where the certificate and pri
 
 ```python
     # X.509 based certificate file
-    cert_file_path = "<certificate file path>"
+    cert_filepath = "<certificate file path>"
     # PKCS#1 or PKCS#8 PEM encoded private key file
     pri_key_filepath = "<private key file path>"
 
@@ -99,8 +99,8 @@ For X509 based mutual TLS, you can create a client where the certificate and pri
     # Create an MQTT5 Client using mqtt5_client_builder
     client = mqtt5_client_builder.mtls_from_path(
         endpoint = "<account-specific endpoint>",
-        cert_filepath=certificate_file_path,
-        pri_key_filepath=private_key_filePath))
+        cert_filepath=cert_filepath,
+        pri_key_filepath=pri_key_filepath))
 ```
 
 #### **Direct MQTT with PKCS12 Method**
@@ -189,4 +189,4 @@ by adding the http_proxy_options keyword argument to the builder:
 ```
 
 SDK Proxy support also includes support for basic authentication and TLS-to-proxy.  SDK proxy support does not include any additional
-proxy authentication methods (kerberos, NTLM, etc...) nor does it include non-HTTP proxies (SOCKS5, for example).
+proxy authentication methods (kerberos, NTLM, etc...) nor does it include non-HTTP proxies (SOCKS5, for example).