Skip to content

Commit

Permalink
Merge pull request #2752 from jandubois/typos-etc
Browse files Browse the repository at this point in the history
Random collection of typo fixes
  • Loading branch information
AkihiroSuda authored Oct 17, 2024
2 parents 26733b7 + 9ad2d74 commit 5c1975c
Show file tree
Hide file tree
Showing 7 changed files with 14 additions and 14 deletions.
2 changes: 1 addition & 1 deletion examples/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,4 +76,4 @@ Lost+found:
- "Tier 1" (marked with ⭐): Good stability. Regularly tested on the CI.
- "Tier 2" (marked with ☆): Moderate stability. Regularly tested on the CI.

Other yamls are tested only occasionally and manually.
Other templates are tested only occasionally and manually.
12 changes: 6 additions & 6 deletions examples/default.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -327,7 +327,7 @@ audio:
# QEMU audiodev, e.g., "none", "coreaudio", "pa", "alsa", "oss".
# VZ driver, use "vz" as device name
# Choosing "none" will mute the audio output, and not play any sound.
# Choosing "default" will pick a suitable of: coreudio, pa, dsound, oss.
# Choosing "default" will pick a suitable choice of: coreaudio, pa, dsound, oss.
# As of QEMU v6.2 the default is to create a disconnected sound device
# that is still visible in the guest but not connected to the host.
# 🟢 Builtin default: ""
Expand Down Expand Up @@ -454,7 +454,7 @@ networks:
# Values must not contain non-printable characters except for spaces and tabs.
# These variables can be referenced as {{.Param.Key}} in lima.yaml.
# In provisioning scripts and probes they are also available as predefined
# environment variables, prefixed with "PARAM` (so `Key` → `$PARAM_Key`).
# environment variables, prefixed with "PARAM_" (so `Key` → `$PARAM_Key`).
# param:
# Key: value

Expand All @@ -463,13 +463,13 @@ networks:
# replace the strings "localhost" and "127.0.0.1" with the host gateway address from inside
# the VM, so it stays routable. Use of the process environment can be disabled by setting
# propagateProxyEnv to false.
# 🟢 Builtn default: true
# 🟢 Builtin default: true
propagateProxyEnv: null

# The host agent implements a DNS server that looks up host names on the host
# using the local system resolver. This means changing VPN and network settings
# are reflected automatically into the guest, including conditional forward,
# and mDNS lookup. By default only IPv4 addresses will be returned. IPv6 addresses
# and mDNS lookup. By default, only IPv4 addresses will be returned. IPv6 addresses
# can only work when using a vmnet network interface and the host has working
# IPv6 configured as well.
hostResolver:
Expand All @@ -486,7 +486,7 @@ hostResolver:
# host.name: host.lima.internal

# If hostResolver.enabled is false, then the following rules apply for configuring dns:
# Explicitly set DNS addresses for qemu user-mode networking. By default qemu picks *one*
# Explicitly set DNS addresses for qemu user-mode networking. By default, qemu picks *one*
# nameserver from the host config and forwards all queries to this server. On macOS
# Lima adds the nameservers configured for the first host interface in service order,
# that has an IPv4 address, to the list. In case this still doesn't work (e.g. VPN
Expand Down Expand Up @@ -519,7 +519,7 @@ plain: null

# A similar mechanism is $LIMA_HOME/_config/override.yaml, which will take
# precedence even over the settings in an instances lima.yaml file.
# It too applies to ALL instances under the same $LIMA_HOME, and is applied
# It also applies to ALL instances under the same $LIMA_HOME, and is applied
# on each restart. It can be used to globally override settings, e.g. make
# the mount of the home directory writable.

Expand Down
2 changes: 1 addition & 1 deletion website/content/en/docs/community/governance/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ Eligibility to be a release manager:
- MUST protect the GPG key with a passphrase or a hardware token.

Release steps:
- Open an issue to propose making a new release. e.g., <https://github.com/lima-vm/lima/issues/2296>.
- Open an issue to propose making a new release, e.g. <https://github.com/lima-vm/lima/issues/2296>.
The proposal should be public, with an exception for vulnerability fixes.
If this is the first time for you to take a role of release management,
you SHOULD make a beta (or alpha, RC) release as an exercise before releasing GA.
Expand Down
2 changes: 1 addition & 1 deletion website/content/en/docs/config/Port/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ LIMA_SSH_PORT_FORWARDER=true limactl start

### Benchmarks

| Usecase | GRPC | SSH |
| Use case | GRPC | SSH |
|-------------|----------------|----------------|
| TCP | 3.80 Gbits/sec | 3.38 Gbits/sec |
| TCP Reverse | 4.77 Gbits/sec | 3.08 Gbits/sec |
Expand Down
4 changes: 2 additions & 2 deletions website/content/en/docs/config/mount/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Lima prior to v0.10 had used "builtin" as the SFTP driver.

#### Caveats
- A mount is disabled when the SSH connection was shut down.
- A compromised `sshfs` process in the guest may have an access to unexposed host directories.
- A compromised `sshfs` process in the guest may have access to unexposed host directories.

### 9p
> **Warning**
Expand Down Expand Up @@ -200,4 +200,4 @@ mounts:

#### Caveats
- For `mountType: 9p`, Inotify events are not triggered for nested files from the listening directory.
- Inotify events are not triggered when files are removed from host
- Inotify events are not triggered when files are removed from host
2 changes: 1 addition & 1 deletion website/content/en/docs/config/multi-arch/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ images:
- location: "https://cloud-images.ubuntu.com/jammy/current/jammy-server-cloudimg-arm64.img"
arch: "aarch64"

# Disable mounts and containerd, otherwise booting up may timeout if the host is slow
# Disable mounts and containerd, otherwise booting up may time out if the host is slow
mounts: []
containerd:
system: false
Expand Down
4 changes: 2 additions & 2 deletions website/content/en/docs/dev/internals/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ The config directory contains global lima settings that apply to all instances.
User identity:

Lima creates a default identity and uses its public key as the authorized key
to access all lima instances. In addition lima will also configure all public
to access all lima instances. In addition, lima will also configure all public
keys from `~/.ssh/*.pub` as well, so the user can use the ssh endpoint without
having to specify an identity explicitly.
- `user`: private key
Expand Down Expand Up @@ -176,7 +176,7 @@ The volume label is "cidata", as defined by [cloud-init NoCloud](https://docs.cl
### Environment variables
- `LIMA_CIDATA_NAME`: the lima instance name
- `LIMA_CIDATA_MNT`: the mount point of the disk. `/mnt/lima-cidata`.
- `LIMA_CIDATA_USER`: the user name string
- `LIMA_CIDATA_USER`: the username string
- `LIMA_CIDATA_UID`: the numeric UID
- `LIMA_CIDATA_HOME`: the guest home directory
- `LIMA_CIDATA_HOSTHOME_MOUNTPOINT`: the mount point of the host home directory, or empty if not mounted
Expand Down

0 comments on commit 5c1975c

Please sign in to comment.