Skip to content

Commit 207036d

Browse files
committed
Fix README typo
1 parent 9e768ab commit 207036d

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Notice how glyph sizes become inconsistent, several glyphs (including most of th
7676

7777
As font problems go, this is pretty minor however. There's even a benefit: this is the first screenshot that shows programming ligatures working (see the row of glyphs just above the emoji faces).
7878

79-
For a whole different scale of font problems, consider `xterm` for example. By default on my Linux system if you just run `xterm`, it will use a low-res `bitmap` "fixed" font with approximately Unicode 3.0 support:
79+
For a whole different scale of font problems, consider `xterm` for example. By default on my Linux system if you just run `xterm`, it will use a low-res **bitmap** "fixed" font with approximately Unicode 3.0 support:
8080

8181
![Screenshot of quick test running on xterm using the Unicode fixed font](docs/images/quick-test-xterm-fixed-unicode-ruler.png)
8282

lib/Terminal/Tests.rakumod

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -135,7 +135,7 @@ row of glyphs just above the emoji faces).
135135
136136
For a whole different scale of font problems, consider C<xterm> for example.
137137
By default on my Linux system if you just run C<xterm>, it will use a low-res
138-
C<bitmap> "fixed" font with approximately Unicode 3.0 support:
138+
B<bitmap> "fixed" font with approximately Unicode 3.0 support:
139139
140140
L<Screenshot of quick test running on xterm using the Unicode fixed font|docs/images/quick-test-xterm-fixed-unicode-ruler.png>
141141

0 commit comments

Comments
 (0)