diff --git a/case-studies/monitoring-logging-case-studies.rst b/case-studies/monitoring-logging-case-studies.rst
index 8f462bab..138f95ed 100644
--- a/case-studies/monitoring-logging-case-studies.rst
+++ b/case-studies/monitoring-logging-case-studies.rst
@@ -23,7 +23,7 @@ to alerts coming from the new infrastructure. She uses a currently
 existing Security Event and Incident Management (SEIM) solution, and
 configures secure logging to the SEIM event collector. Alice and the SOC
 analyst build the SEIM views so that logs are correlated by type, and
-trigger alerts on unexpected or “interesting” events, such as a
+trigger alerts on unexpected or "interesting" events, such as a
 successful login by a user immediately after a string of failed login
 attempts within a given timeframe. The SOC analyst is also given
 escalation protocols and contact information so that when an specific
diff --git a/security-guide/source/dashboard/checklist.rst b/security-guide/source/dashboard/checklist.rst
index d2cd7bdc..6c6a0f93 100644
--- a/security-guide/source/dashboard/checklist.rst
+++ b/security-guide/source/dashboard/checklist.rst
@@ -127,7 +127,7 @@ Recommended in: :doc:`cookies`.
 Check-Dashboard-06: Is ``SESSION_COOKIE_HTTPONLY`` parameter set to ``True``?
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-The “HTTPONLY” cookie attribute instructs web browsers not to allow scripts
+The "HTTPONLY" cookie attribute instructs web browsers not to allow scripts
 (e.g. JavaScript or VBscript) an ability to access the cookies via the DOM
 ``document.cookie`` object. This session ID protection is mandatory to prevent
 session ID stealing through XSS attacks.
diff --git a/security-threat-analysis/source/architecture-diagram-guidance.rst b/security-threat-analysis/source/architecture-diagram-guidance.rst
index a46cb734..c576f8c8 100644
--- a/security-threat-analysis/source/architecture-diagram-guidance.rst
+++ b/security-threat-analysis/source/architecture-diagram-guidance.rst
@@ -50,7 +50,7 @@ Service Architecture diagrams contain these elements:
       types
 
       -  A vertical cylinder indicates storage or a database
-      -  A horizontal cylinder (a “pipe” shape) indicates a message
+      -  A horizontal cylinder (a "pipe" shape) indicates a message
          queue (use an elongated rectangle if horizontal cylinders are
          unavailable)
 
diff --git a/security-threat-analysis/source/threat-analysis-process.rst b/security-threat-analysis/source/threat-analysis-process.rst
index 3dbc1da1..b94e7790 100644
--- a/security-threat-analysis/source/threat-analysis-process.rst
+++ b/security-threat-analysis/source/threat-analysis-process.rst
@@ -54,7 +54,7 @@ Before the review
 Running the threat analysis review
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- Identify the “scribe” role, who will record the discussion and any
+- Identify the "scribe" role, who will record the discussion and any
   findings in the etherpad.
 - Ask the project architect to briefly describe the purpose of the service,
   typical uses cases, who will use it and how it will be deployed.