Updates comms and list guidelines.

2 files changed, 11 insertions, 27 deletions

diff --git a/note/comms.html b/note/comms.html
index 5055a86..aa9e0a6 100644
--- a/note/comms.html
+++ b/note/comms.html
@@ -10,33 +10,17 @@
 		<h1>Communication Guidelines</h1>
 		<p><a href="/contact.html">A few ways to contact me</a></p>
 		<p>
-		These are some general recommendations that I believe make communicating with me, at least, easier and/or more effective, including communication conventions that make me happier :D.  Please note that what I prefer may not be what others prefer and shall not be treated as a general guideline for communications.
+		These are some general recommendations that I believe make communicating with me, at least, easier and/or more effective, including communication conventions that make me happier.  Please note that what I prefer may not be what others prefer and shall not be treated as a general guideline for communications.
 		</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>
-			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&mdash;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.  Do not hard-wrap Chinese.
-			</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>
+			<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>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&mdash;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.</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>
 		</ol>
 		<div id="footer">
 			<hr />
diff --git a/note/mailing-list-guidelines.html b/note/mailing-list-guidelines.html
index 9224d2f..245d218 100644
--- a/note/mailing-list-guidelines.html
+++ b/note/mailing-list-guidelines.html
@@ -8,7 +8,7 @@
 	</head>
 	<body class="indent">
 		<h1><code>andrewyu.org</code> Mailing List Guidelines</h1>
-		The following guidelines apply to most <a href="https://mail.andrewyu.org/mailman/listinfo">public mailing lists on <code>andrewyu.org</code></a>.  Different lists may have different specific guidelines.
+		<p>The following guidelines apply to most <a href="https://mail.andrewyu.org/mailman/listinfo">public mailing lists on <code>andrewyu.org</code></a>.  Different lists may have different specific guidelines.</p>
 		<ul>
 			<li>
 				Be considerate of other subscribers on the mailing lists.
@@ -26,7 +26,7 @@
 			<li>
 				Trim your signature.
 				<br />
-				Keep the signature lines at the bottom of your mail to a reasonable length. PGP signatures and those automatic address cards are merely annoying and are stripped out. Legal disclaimers and advisories are also very annoying, and inappropriate for public mailing lists.
+				Keep the signature lines at the bottom of your mail to a reasonable length.  PGP signatures should be attachments rather than inline.
 			</li>
 			<li>
 				Stay on topic.