Documentation: Correct some typos in kernel and browser docs

This commit is contained in:
Siddhant Rao 2021-06-02 19:10:41 +05:30 committed by Andreas Kling
parent ea7ba34a31
commit 566d3cb393
Notes: sideshowbarker 2024-07-18 17:00:44 +09:00
2 changed files with 4 additions and 4 deletions

View file

@ -12,7 +12,7 @@ Every instance of the **Browser** application can have one or more tabs open. Ea
Two important aspects of web browsing are further separated from the **WebContent** process: *network requests* and *image decoding*, segregated to the **RequestServer** and **ImageDecoder** processes respectively.
All processes and are aggressively sandboxed using the `pledge()` and `unveil()` mechanisms. Furthermore, all processes except **Browser** run as an unprivileged user, separate from the primary logged-in desktop user.
All processes are aggressively sandboxed using the `pledge()` and `unveil()` mechanisms. Furthermore, all processes except **Browser** run as an unprivileged user, separate from the primary logged-in desktop user.
### Process: WebContent
@ -26,7 +26,7 @@ For DNS lookups, **RequestServer** asks for help from the system's global **Look
### Process: ImageDecoder
This process can decode images (PNG, JPEG, BMP, ICO, PBM, etc.) into bitmaps. Each image is decoded in a fresh **ImageDecoder** process. These are strongly sandboxed and can't do much except receive encoded bitmap data and return a bitmap to **WebContent** if decoding successful.
This process can decode images (PNG, JPEG, BMP, ICO, PBM, etc.) into bitmaps. Each image is decoded in a fresh **ImageDecoder** process. These are strongly sandboxed and can't do much except receive encoded bitmap data and return a bitmap to **WebContent** if decoding is successful.
### How processes are spawned

View file

@ -16,7 +16,7 @@ Locker locker(m_lock);
return true;
```
This lock doesn't disable interrupts at all, and if it already in use, the scheduler will simply yield away from that section until it tries to lock it again.
This lock doesn't disable interrupts at all, and if it is already in use, the scheduler will simply yield away from that section until it tries to lock it again.
### Hard lock - `SpinLock<u8>`
@ -31,7 +31,7 @@ ScopedSpinLock lock(m_lock);
return true;
```
### Why we need soft and hard locking in the AHCI code?
### Why do we need soft and hard locking in the AHCI code?
First of all, the proper way of taking a `SpinLock` and `Lock` is to:
```c++