finalized annotation and notes of where the code is not working. also started editing the print.css file, but the adding the fonts to the inferior e-reader did not work. to be checked out tomorrow ( ͡° ͜ʖ ͡°)

print.css

@@ -16,8 +16,17 @@ mark {
     background: yellow;
     display: block;
     clear:both;
+    padding-left: 0.5cm;
+    font-family: DuctusRegular;
+}
+h1{
+   font-family: DuctusRegular; 
 }
 
 code {
     font-family: monospace;
+}
+
+p {
+    font-family:CascadiaCode_VTT;
 }

templates/book.jinja

@@ -47,7 +47,7 @@
     <p>{{ since_last_boot }}</p>
     {% if since_last_boot is defined %}
     <mark>
-      {% if days_since_last_boot|int > 14 %}This is unusual, we are used to our server crashing quite often, especially when we are all sharing the space and editing at the same time. Our server, chopchop, chops up time into small bits of surprise in which we learn that the technologies we rely on are never just up and running on their own. They require people to care for them, to put in the time and the mindspace to figure out how to keep them running and available.{% else %}This is common, the fragility of these machines are more prominent than any cloud user expects. Partially because of scale, partially because a lot of labour that happens in datacenters just escapes us all when we want to just upload an image, or just send a message, or just open a webpage.{% endif %}
+      {% if days_since_last_boot|int > 14 %}This is unusual, we are used to our server crashing quite often, especially when we are all sharing the space and editing at the same time. Our server, chopchop, chops up time into small bits of surprise in which we learn that the technologies we rely on are never just up and running on their own. They require people to care for them, to put in the time and the mindspace to figure out how to keep them running and available.{% else %}This short of an uptime is common, the fragility of these machines are more prominent than any cloud user expects. Partially because of scale, partially because a lot of labour that happens in datacenters just escapes us all when we want to just upload an image, or just send a message, or just open a webpage.{% endif %}
     </mark>
     {% endif %}
 
@@ -59,16 +59,13 @@
         <mark>
       {% if users_created_today|length > 0 %}{{last_user_name}} user was added, and the network of trust grew ever so slightly. Users will be trusted with not just the keys and passwords to the "house" which is the server, but with a
       portion of responsibility to keep it afloat and contribute to what makes it a community of practices (and
-      network of knowledge and dependence).
-        </mark>
-      {% endif %}
-        <mark>
-      {% if users_created_today|length < 0 %} No new users were created today. The trust network remains the dame size.{% endif %}
+      network of knowledge and dependence).{% else %}No new users were created today. The trust network remains the same size.{% endif %}
         </mark>
         {% endif %}
 
-    {% if list_package_installs|length > 0 %}
+      {% if list_package_installs|length > 0 %}
     <pre><em>tldr@chopchop:~ $</em> grep 'install' /var/log/dpkg.log</pre>
+      <b>Something here in the if statement is not working</b>
     <ul>
         <mark>
       Today the following packages were installed:
@@ -85,10 +82,12 @@
         <mark>
       Today no new packages were installed...
         </mark>
+        <b>This part also not working</b>
     {% endif %}
 
     {% if list_package_upgrade|length > 0 %}
     <pre><em>tldr@chopchop:~ $</em> grep 'upgrade' /var/log/dpkg.log</pre>
+        <b>Something here in the if statement is not working</b>
       <mark>
       Out of the installed packages, these ones were upgraded:
         </mark>
@@ -117,8 +116,9 @@
       <li>{{ item }}</li>
       {% endfor %}
         <mark>
-          Packages could be removed because of consuming too much storage, not being used by the people who share the server, or they are no longer secure. It is often good practice to 'do some spring cleaning' every now and then and remove the packages that no longer serve you any purpose.  
+          Packages could be removed because of consuming too much storage, not being used by the people who share the server, or they are no longer secure. It is often good practice to 'do some spring cleaning' every now and then and remove the packages that no longer serve you any purpose.
         </mark>
+          <b>Does not show this last mark statement after the list</b>
     </ul>
     {% endif %}
     {% if list_package_remove|length < 0 %}
@@ -138,11 +138,13 @@
       <li>{{ item }}</li>
       {% endfor %}
     </ul>
+        <b>does not show the users of logins_today</b>
     <mark>
       These users have logged into our shared server chopchop, during the course of this day. 
     </mark>
       {% endif %}
 
+        {% if groups_created|length > 0 %}
     <pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=groupadd -r --output-fields=MESSAGE</pre>
     <mark>
         This command shows whether groups were added today.
@@ -155,6 +157,13 @@
         </mark>
       {% endfor %}
     </ul>
+        {% endif %}
+        {% if groups_created|length < 0 %}
+        <mark>
+        No groups were added today.
+        </mark>
+        {% endif %}
+            <b>For some reason this if statement is not working, i didn't apply it to the next 4 categories because i wanted to check it works first</b>
 
     <pre><em>tldr@chopchop:~ $</em>sudo journalctl _COMM=groupremove -r --output-fields=MES</pre>
     <mark>
@@ -199,7 +208,8 @@
 
     <pre><em>tldr@chopchop:~ $</em>sudo service --status-all</pre>
     <mark>
-        All of the service that are active running, + running, - idle, not running.
+        These are all of the services that are active, running, working to execute requests that enable everything on the server. They are marked with an [+].
+The rest, marked with a [-], are idle, not running, or waiting to be activating upon sending a request.
       </mark>
       <ul>
       {% for item in list_active_services %}