From 0557a04be146ee19f2350cb9d912537776547cb5 Mon Sep 17 00:00:00 2001
From: Brett Nicholas <7547222+bigbrett@users.noreply.github.com>
Date: Mon, 18 Mar 2024 08:30:25 -0600
Subject: [PATCH] Update chapter06.md

---
 wolfSSL/src/chapter06.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/wolfSSL/src/chapter06.md b/wolfSSL/src/chapter06.md
index 86f6d5f9..33da7f0b 100644
--- a/wolfSSL/src/chapter06.md
+++ b/wolfSSL/src/chapter06.md
@@ -221,7 +221,7 @@ WOLFSSL_API int wc_CryptoCb_RegisterDevice(int devId,
 
 #### 3. Pass the `devId` as an argument to a wolfCrypt API function
 
-For wolfCrypt API’s use the init functions that accept “devId” such as:
+For wolfCrypt API’s use the init functions that accept `devId` such as:
 ```
 wc_InitRsaKey_ex
 wc_ecc_init_ex
@@ -234,7 +234,7 @@ wc_InitCmac_ex
 This is not an exhaustive list. Please refer to the wolfCrypt API documentation to see if a particular algorithm supports crypto callbacks. 
 
 #### 4. (TLS only): associate the devId with your WOLFSSL context
-To enable use of a crypto callback when using TLS, you must supply the “devId” arguments on initialization of a `WOLFSSL_CTX` or `WOLFSSL` struct.
+To enable use of a crypto callback when using TLS, you must supply the `devId` arguments on initialization of a `WOLFSSL_CTX` or `WOLFSSL` struct.
 ```
 wolfSSL_CTX_SetDevId(ctx, devId);
 wolfSSL_SetDevId(ssl, devId);