RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-27 14:17:36 +00:00
Code Issues Activity Actions

Everywhere: Fix spelling mistakes

Browse source
This commit is contained in:
mjz19910 2022-01-07 05:04:05 -07:00 • committed by Linus Groh
parent 168063819d
commit 10ec98dd38
56 changed files with 90 additions and 90 deletions
Download patch file Download diff file Expand all files Collapse all files

2
Documentation/BuildInstructionsMacOS.md
View file

@ -2,7 +2,7 @@
# Prerequisites
This installation guide assumes that you have [Homebrew](https://brew.sh) and Xcode installed. You need to open Xcode atleast once for it to install the required tools.
This installation guide assumes that you have [Homebrew](https://brew.sh) and Xcode installed. You need to open Xcode at least once for it to install the required tools.
Before you build, you must set your command line tools to Xcode's tools instead of the ones installed via Homebrew:
```console

4
Documentation/NetworkBoot.md
View file

@ -10,7 +10,7 @@ This guide assumes several things:
- The TFTP server root is `/srv/tftp/`
- Bootloaders are located inside `/srv/tftp/boot/`
- SerenityOS artefacts are located inside `/srv/tftp/serenity/`:
- SerenityOS artifacts are located inside `/srv/tftp/serenity/`:
- The prekernel is located at `/srv/tftp/serenity/prekernel`
- You can find it at `Build/i686/Kernel/Prekernel/Prekernel`
- The kernel is located at `/srv/tftp/serenity/kernel`
@ -134,7 +134,7 @@ LABEL SerenityOS
### Troubleshooting
- Issues with DHCP or TFTP usually require sniffing packets on the network to figure out.
- TFTP is a slow protocol, transferring the QEMU disk image (~ 200 MiB) will take some time. Consider setting up a FTP or HTTP server for faster downloading of SerenityOS artefacts if your bootloader supports it.
- TFTP is a slow protocol, transferring the QEMU disk image (~ 200 MiB) will take some time. Consider setting up a FTP or HTTP server for faster downloading of SerenityOS artifacts if your bootloader supports it.
- Remember that SerenityOS has not been extensively tested on physical hardware.
- Some BIOS implementations of PXE are buggy or some machines may not have a PXE boot option at all in which case you could try using [iPXE](https://ipxe.org/).
- Virtual machines can also be booted over the network. Cheat notes for QEMU on Linux, assuming `br0` is already set up:

2
Documentation/Patterns.md
View file

@ -234,7 +234,7 @@ See: https://en.cppreference.com/w/cpp/utility/source_location
`AK::SourceLocation` is the implementation of this feature in
SerenityOS. It's become the idiomatic way to capture the location
when adding extra debugging instrumentation, without resorting to
litering the code with preprocessor macros.
littering the code with preprocessor macros.
To use it, you can add the `AK::SourceLocation` as a default argument
to any function, using `AK::SourceLocation::current()` to initialize the

2
Documentation/SelfHostedRunners.md
View file

@ -63,7 +63,7 @@ RUST_WHITELISTED_EVENT_NAME=push
```shell
MAX_RUNNER_THREADS=XXX
```
If you are setting up multiple runners on the same machine, this setting can be used to divvy up the cores, if youre only setting up one runner, this can just be set to the server's core count
If you are setting up multiple runners on the same machine, this setting can be used to divvy up the cores, if you're only setting up one runner, this can just be set to the server's core count
### Install the runner as a service
```shell
sudo ./svc.sh install