[git commit] use_less_ram.html: typo fix

[Denys Vlasenko]

commit: https://git.busybox.net/busybox-website/commit/?id=32f5bead1bcc80325831c7ef4b53d59f79a1ed78
branch: https://git.busybox.net/busybox-website/commit/?id=refs/heads/master

Signed-off-by: Denys Vlasenko <vda.linux at googlemail.com>
---
 use_less_ram.html | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/use_less_ram.html b/use_less_ram.html
index 5dfe04f..7546875 100644
--- a/use_less_ram.html
+++ b/use_less_ram.html
@@ -32,7 +32,7 @@ RW pages, both data and bss, exist as separate copies for each process.
 (They may be shared as long as they are not modified. However,
 well-designed programs don't put constant data into RW sections,
 therefore in practice almost all RW data or bss pages which were
-touched by the program are modified).
+touched by the program are modified, and therefore not shared).
 </p><p>
 When process starts executing, two more mappings appear. One is the stack.
 It is usually located ner the top of virtual address space, and contains
@@ -63,11 +63,11 @@ ff82a000     132K rw-p  [stack]       - stack</pre>
 It is important to minimize the number of RW pages your program touches.
 Data, bss and stack pages are never freed, therefore for large,
 and especially for temporary allocations, it's best to use malloc()
-or mmap(). One way to use fewer RW pages is to _have_ fewer RW pages
+or mmap(). One way to use fewer RW pages is to <b>have</b> fewer RW pages
 in your binary. There are several scenarios when a binary may end up having
 more data+bss pages than necessary.
 </p><p>
-It is possible to have a Busybox binary with almost all apllets and only
+It is possible to have a Busybox binary with almost all applets and only
 8 kilobytes of data+bss.
 </p>
 <h4>Optimizing start of data</h4>