Clarify WebSocket restriction rule's impact on static serving

Before this change, the rule technically disallows implementing JavaScript clients because webbrowsers use HTTP to fetch the static files.

This commit also fixes a mistake in a previous commit where Markdown-style characters were used instead of code-tags.

1 files changed, 3 insertions, 1 deletions

diff --git a/pydis_site/templates/events/pages/code-jams/9/rules.html b/pydis_site/templates/events/pages/code-jams/9/rules.html
index 5ad75d67..3e610ff2 100644
--- a/pydis_site/templates/events/pages/code-jams/9/rules.html
+++ b/pydis_site/templates/events/pages/code-jams/9/rules.html
@@ -17,10 +17,12 @@
 
         <p>
             An exception to this rule is that communication with databases and files is allowed for accessing resources or for storage purposes.
-            For example, you may use PostgreSQL as a database but not its `NOTIFY` command.
+            For example, you may use PostgreSQL as a database but not its <code>NOTIFY</code> command.
             Working with subprocesses (through stdin/stdout or <code>multiprocessing.Pool()</code>/<code>concurrent.futures.ProcessPoolExecutor()</code>) is also allowed.
         </p>
 
+        <p>Another exception is made for serving static files, which normally uses HTTP. You are also allowed to serve a JavaScript-implemented client for your WebSocket server.</p>
+
         <p>If you're interested in utilizing a particular non-WebSocket method of communication, reach out to the Events Team for discussion and approval</p>
     </li>
     <li><p>Your solution should be platform agnostic. For example, if you use filepaths in your submission, use <code>pathlib</code> to create platform agnostic Path objects instead of hardcoding the paths.</p></li>