Bluetooth: ATT: Fix non-ASCII characters in code comments

Change-Id: Ief28ffbab1f1751344184b35e40f32e1fc1d6ac9 Signed-off-by: Szymon Janc <[email protected]>
niziak · Nov 11, 2016 · 27cbd58 · 27cbd58
1 parent f2b1ffb
commit 27cbd58
Showing 1 changed file with 7 additions and 7 deletions.
diff --git a/subsys/bluetooth/host/att.c b/subsys/bluetooth/host/att.c
@@ -1448,8 +1448,8 @@ static int att_change_security(struct bt_conn *conn, uint8_t err)
 			 * page 375:
 			 *
 			 * If an LTK is not available, the service request
-			 * shall be rejected with the error code “Insufficient
-			 * Authentication”.
+			 * shall be rejected with the error code 'Insufficient
+			 * Authentication'.
 			 * Note: When the link is not encrypted, the error code
 			 * "Insufficient Authentication" does not indicate that
 			 * MITM protection is required.
@@ -1462,11 +1462,11 @@ static int att_change_security(struct bt_conn *conn, uint8_t err)
 			 * If an authenticated pairing is required but only an
 			 * unauthenticated pairing has occurred and the link is
 			 * currently encrypted, the service request shall be
-			 * rejected with the error code “Insufficient
-			 * Authentication.”
+			 * rejected with the error code 'Insufficient
+			 * Authentication'.
 			 * Note: When unauthenticated pairing has occurred and
 			 * the link is currently encrypted, the error code
-			 * “Insufficient Authentication” indicates that MITM
+			 * 'Insufficient Authentication' indicates that MITM
 			 * protection is required.
 			 */
 			sec = BT_SECURITY_HIGH;
@@ -1477,8 +1477,8 @@ static int att_change_security(struct bt_conn *conn, uint8_t err)
 			 * If LE Secure Connections authenticated pairing is
 			 * required but LE legacy pairing has occurred and the
 			 * link is currently encrypted, the service request
-			 * shall be rejected with the error code “Insufficient
-			 * Authentication”.
+			 * shall be rejected with the error code ''Insufficient
+			 * Authentication'.
 			 */
 			sec = BT_SECURITY_FIPS;
 		} else {