diff --git a/note/comms.html b/note/comms.html
index e934bc1..1c75230 100644
--- a/note/comms.html
+++ b/note/comms.html
@@ -14,10 +14,10 @@
 		</p>
 		<ol>
 			<li>Write a descriptive subject for emails.  Do not send emails with an empty subject or no subject header.  The subject should be give the receiver a brief idea of what the email is about.</li>
-			<li>Send complete information.  When telling me something or requesting something, please provide complete background information, knowledge required, and other relevant context.  This prevents back-and-forth communication along the lines of ``and now I need to know ... but you didn't tell me that so can you please give that to me''.  Providing context defragments conversations which increases efficiency.</li>
+			<li>Send complete information.  When telling me something or requesting something, please provide complete background information, knowledge required, and other relevant context.  This prevents back-and-forth communication along the lines of &ldquo;and now I need to know ... but you didn't tell me that so can you please give that to me&rdquo;.  Providing context defragments conversations which increases efficiency.</li>
 			<li>When using instant messaging such as IRC, do not split one sentence into multiple messages.  Fragmentation reduces readability.</li>
 			<li>Do not use excessive emojis.</li>
-			<li>Be direct.  As the sender, do not use polite expressions like ``you did quite well in that presentation'' when in reality, the sender believes that the presentation is not ``quite well''.  Direct critique and suggestions are very welcome here.  Politeness is acceptable if it does not interfere with honest conveying of information.</li>
+			<li>Be direct.  As the sender, do not use polite expressions like &ldquo;you did quite well in that presentation&rdquo; when in reality, the sender believes that the presentation is not &ldquo;quite well&rdquo;.  Direct critique and suggestions are very welcome here.  Politeness is acceptable if it does not interfere with honest conveying of information.</li>
 			<li><a href="./ask.html">Don't ask to ask.</a></li>
 			<li>Use plain text email.  Both hard-wrapped and non-hard-wrapped emails are acceptable.  If you do hard-wrap, please wrap at 72 characters for English.  Chinese, if hard-wrapped, should be at 36 characters.  Non hard-wrapped emails should <a href="https://www.ietf.org/rfc/rfc3676.txt">specify format=flowed as per RFC3676</a>.</li>
 			<li>Interweave the original message with the response when replying to an email and remove irrelevant parts (i.e. greetings, closings, signatures, etc.) of the quoted original email.</li>