Skip to content

Commit 0fb5f15

Browse files
committed
README: Fix typos
1 parent 450daca commit 0fb5f15

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ Features
5757
* Very trivial module loading support (**no** automatic dependency
5858
resolution).
5959

60-
When compiled on a x86_64 system with the default `-Og` compiler flags,
60+
When compiled on an x86_64 system with the default `-Og` compiler flags,
6161
statically linked against dietlibc 0.33~cvs20120325-6, the binary
6262
stripped and the resulting initramfs (without any modules added)
6363
compressed with `gzip -9`, the images produced are between 9 kiB and
@@ -328,15 +328,15 @@ many buffers that the amount of RAM used is a concern just yet, even
328328
for small systems), so that no real flexibility is sacrificed.
329329

330330
None of this is extremely performance-critical (it is going to be quite
331-
fast regardless, because very little is done compared to a even just
331+
fast regardless, because very little is done compared to even just
332332
running a shell), so no algorithm is optimized for speed directly. For
333333
example, the mount option parser table is somewhat compressed to reduce
334334
the code size (negation and recursive variants of mount options are not
335335
repeated), to the point where further reduction would likely sacrifice
336336
the readability of the code. Execution speed is achieved by doing very
337337
little, not by micro-optimizing algorithms.
338338

339-
Some times it is necessary to reimplement certain libc functios because
339+
Sometimes it is necessary to reimplement certain libc functions because
340340
using the libc variants increase the image size too much. For example,
341341
using `inet_ntoa` and `inet_aton` (to convert between ASCII to binary
342342
representations of IP addresses) from the musl C library will cause
@@ -371,7 +371,7 @@ be interesting regardless:
371371
file systems.
372372

373373
Note that the goal is to keep the `initrd.img` size smaller than 16 KiB
374-
on all plattforms, so a cutoff of 15 KiB is used on x86_64, to leave
374+
on all platforms, so a cutoff of 15 KiB is used on x86_64, to leave
375375
room for different assembly code sizes etc., at least when used in a
376376
minimal configuration. Therefore, some features (such as `UUID=` and
377377
NFSv4 support) are compile-time optional.

0 commit comments

Comments
 (0)