Normal quotes

35-05.md

@@ -34,7 +34,7 @@ Enable Set/Reset and Set/Reset registers for each pixel: While
 modularity would improve, speed would suffer markedly.
 
 ![](images/35-05.jpg)\
- **Figure 35.5**  *EVGALine’s decision logic.*
+ **Figure 35.5**  *EVGALine's decision logic.*
 
 #### Drawing Each Line {#Heading8}
 
@@ -73,7 +73,7 @@ At the core of **Octant0** and **Octant1** is a pixel-drawing function,
 **EVGADot**. **EVGADot** draws a pixel at the specified coordinates in
 whatever color the hardware of the VGA happens to be set up for. As
 described earlier, since the entire line drawn by **EVGALine** is of the
-same color, line-drawing performance is improved by setting the VGA’s
+same color, line-drawing performance is improved by setting the VGA's
 hardware up once in **EVGALine** before the line is drawn, and then
 drawing all the pixels in the line in the same color via **EVGADot**.
 
@@ -93,14 +93,14 @@ bitmap starting at address A000:0000, with the pixel at the upper left
 of the screen controlled by bit 7 of the byte at offset 0, the next
 pixel to the right controlled by bit 6, the ninth pixel controlled by
 bit 7 of the byte at offset 1, and so on. Further, it assumes that the
-graphics adapter’s hardware is configured such that setting the Bit Mask
+graphics adapter's hardware is configured such that setting the Bit Mask
 register to allow modification of only the bit controlling the pixel of
 interest and then ORing a value of 0FEH with display memory will draw
 that pixel correctly without affecting any other dots. (Note that 0FEH
 is used rather than 0FFH or 0 because some optimizing compilers turn ORs
 with the latter values into simpler operations or optimize them away
-entirely. As explained later, however, it’s not the value that’s ORed
-that matters, given the way we’ve set up the VGA’s hardware; it’s the
+entirely. As explained later, however, it's not the value that's ORed
+that matters, given the way we've set up the VGA's hardware; it's the
 act of ORing itself, and the value 0FEH forces the compiler to perform
 the OR operation.) Again, this is the normal way in which modes 0EH,
 0FH, 10H, and 12H operate. As described earlier, **EVGADot** also
@@ -117,10 +117,10 @@ the one that controls the pixel to be drawn will be left unmodified.
 
 Finally, 0FEH is ORed with the display memory byte controlling the pixel
 to be drawn. ORing with 0FEH first reads display memory, thereby loading
-the VGA’s internal latches with the contents of the display memory byte
+the VGA's internal latches with the contents of the display memory byte
 controlling the pixel to be drawn, and then writes to display memory
-with the value 0FEH. Because of the unusual way in which the VGA’s data
-paths work and the way in which **EVGALine** sets up the VGA’s Enable
+with the value 0FEH. Because of the unusual way in which the VGA's data
+paths work and the way in which **EVGALine** sets up the VGA's Enable
 Set/Reset and Set/Reset registers, the value that is written by the
 **OR** instruction is ignored. Instead, the value that actually gets
 placed in display memory is the color that was passed to **EVGALine**