Unix_Concepts: Only mark up I/O operations as code and not commaHEADmaster

Currently, the spacing is a little off, because the comma is also marked
up as code. So only mark up the I/O operations.

Signed-off-by: Andre Noll <maan@tuebingen.mpg.de>

1 files changed, 6 insertions, 5 deletions

diff --git a/Unix_Concepts.m4 b/Unix_Concepts.m4
index 7f0b5d8..fb3a122 100644
--- a/Unix_Concepts.m4
+++ b/Unix_Concepts.m4
@@ -557,8 +557,8 @@ EXERCISES()
 HOMEWORK(«
 
 Think about printers, sound cards, or displays as a file. Specifically,
-describe what <code>open, read</code>, and <code>write</code> should
-mean for these devices.
+describe what <code>open</code>, <code>read</code>, and <code>write</code>
+should mean for these devices.
 
 », «
 
@@ -570,9 +570,10 @@ printers could return the number of paper trays, the amount of toner
 left etc. Writing to the file descriptor would cause output on the
 device. This would mean to print the text that is written, play the
 audio samples, or show the given text on the display. The point to
-take away is that the <code>open, read, write</code> interface is a
-generic concept that works for different kinds of devices, not only
-for storing data in a file on a hard disk.
+take away is that the <code>open</code>, <code>read</code>,
+<code>write</code> interface is a generic concept that works for
+different kinds of devices, not only for storing data in a file on a
+hard disk.
 
 »)