Fix typo in `across`.

Signed-off-by: apostasie <spam_blackhole@farcloser.world>
This commit is contained in:
apostasie 2025-06-06 13:34:48 -07:00
parent 81c6a301c2
commit f38310bb9e
No known key found for this signature in database
3 changed files with 3 additions and 3 deletions

View File

@ -255,7 +255,7 @@ On a warm cache, it is still over 150MB and 30+ seconds.
In and of itself, this is hard to reduce, as we need these...
Actions:
- [ ] we could cache the module download location to reduce round-trips on modules that are shared accross
- [ ] we could cache the module download location to reduce round-trips on modules that are shared across
different projects
- [ ] we are likely installing nerdctl modules six times - (once per architecture during the build phase, then once per
ubuntu version and architecture during the tests runs (this is not even accounted for in the audit above)) - it should

View File

@ -23,7 +23,7 @@ containers can be named the same), etc.
However, storing data on the filesystem in a reliable way comes with challenges:
- incomplete writes may happen (because of a system restart, or an application crash), leaving important structured files
in a broken state
- concurrent writes, or reading while writing would obviously be a problem as well, be it accross goroutines, or between
- concurrent writes, or reading while writing would obviously be a problem as well, be it across goroutines, or between
concurrent executions of the nerdctl binary, or embedded in a third-party application that does concurrently access resources
The `pkg/store` package does provide a "storage" abstraction that takes care of these issues, generally providing

View File

@ -65,7 +65,7 @@ Data volume
Can be overridden with `nerdctl --cni-netconfpath=<NETCONFPATH>` flag and environment variable `$NETCONFPATH`.
At the top-level of <NETCONFPATH>, network (files) are shared accross all namespaces.
At the top-level of <NETCONFPATH>, network (files) are shared across all namespaces.
Sub-folders inside <NETCONFPATH> are only available to the namespace bearing the same name,
and its networks definitions are private.