From 5bbf1aeb170c7f39ebafcbb59d58d0d2d16fd34f Mon Sep 17 00:00:00 2001 From: Matthew Butterick Date: Sun, 28 Apr 2019 10:29:49 -0700 Subject: [PATCH] unlink --- xenomorph/xenomorph/scribblings/xenomorph.scrbl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xenomorph/xenomorph/scribblings/xenomorph.scrbl b/xenomorph/xenomorph/scribblings/xenomorph.scrbl index 60d13192..34c89c35 100644 --- a/xenomorph/xenomorph/scribblings/xenomorph.scrbl +++ b/xenomorph/xenomorph/scribblings/xenomorph.scrbl @@ -117,7 +117,7 @@ The key point: the @litchar{#"} prefix tells us we're looking at a byte string, Back to files. Files are classified as being either @deftech{binary} or @deftech{text}. (A distinction observed by Racket functions such as @racket[write-to-file].) When we speak of binary vs. text, we're saying something about the internal structure of the byte sequence — what values those bytes represent. We'll call this internal structure the @deftech{binary format} of the file. -@margin-note{This internal structure is also called an @tech{encoding}. Here, however, I avoid using that term as a synonym for @tech{binary format}, because I prefer to reserve it for when we talk about encoding and decoding as operations on data.} +@margin-note{This internal structure is also called an @emph{encoding}. Here, however, I avoid using that term as a synonym for @tech{binary format}, because I prefer to reserve it for when we talk about encoding and decoding as operations on data.} @;{ @subsubsection{Text encodings}