fix(typos): Fix first round of typos from spellcheck upgrade

ananos · ananos · commit 442556b4b3b0 · 2025-07-25T16:58:06.000+03:00
This is the first round of typos that our spellcheck upgrade
found. I suspect, as we go, we should find more in the newly
added dictionary and fix them appropriately.

Signed-off-by: Anastassios Nanos &lt;ananos@nubificus.co.uk&gt;
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -154,7 +154,7 @@
 - ([1ae5d5b](https://github.com/nubificus/urunc/commit/1ae5d5ba514a061bf14dbf01035a986b5cfb26e4)) Update installation instructions, add linting instructions (@gntouts)
 
 - ([89fa71c](https://github.com/nubificus/urunc/commit/89fa71cc35f0bb3ce019e4c7b861dd43f49ead6b)) Add tests, update workflow triggers (@gntouts)
-    - Add end to end tests for hvt hypervisor and rumprun unikernels using ctr, nerdct, crictl.
+    - Add end to end tests for hvt hypervisor and rumprun unikernels using ctr, nerdctl, crictl.
 
 - ([9271e4f](https://github.com/nubificus/urunc/commit/9271e4f2dd667c4c23b716ec10010ec6d7759671)) Refactor urunc to enhance code organization and maintainability (@gntouts)
 
diff --git a/Makefile b/Makefile
@@ -104,7 +104,7 @@ INSTALL_DEPS   += $(shell test -e $(SHIM_BIN)_static_$(ARCH) \
 
 # Main Building rules
 #
-# By default we opt to build static binaries targeting the host archiotecture.
+# By default we opt to build static binaries targeting the host architecture.
 # However, we build shim as a dynamically-linked binary.
 
 ## default Build shim and urunc statically for host arch.(default).
@@ -143,8 +143,8 @@ dynamic: $(URUNC_BIN)_dynamic_$(ARCH) $(SHIM_BIN)_dynamic_$(ARCH)
 .PHONY: all
 all: $(SHIM_BIN)_static_arm64 $(SHIM_BIN)_static_amd64 $(URUNC_BIN)_static_amd64 $(URUNC_BIN)_static_arm64
 
-# Just an alias for $(VENDOR_DIR) for easie invocation
-## prepare Run go mod vendor and veridy.
+# Just an alias for $(VENDOR_DIR) for easy invocation
+## prepare Run go mod tidy, vendor, and verify.
 prepare: $(VENDOR_DIR)
 
 # Add tidy as order-only prerequisite. In that way, since tidy does not
@@ -156,7 +156,7 @@ $(VENDOR_DIR):
 	$(GO) mod verify
 
 # Add tidy and as order-only prerequisite. In that way, since tidy and
-# vendor do notproduce any file and execute all the time,
+# vendor do not produce any file and execute all the time,
 # we avoid the rebuilding of urunc if it has previously built and the
 # source files have not changed.
 $(URUNC_BIN)_static_%: $(URUNC_SRC) | prepare
diff --git a/cmd/urunc/create.go b/cmd/urunc/create.go
@@ -168,7 +168,7 @@ func createUnikontainer(context *cli.Context) (err error) {
 	// TODO: This part of code needs better rhandling. It is not the
 	// job of the urunc create to setup the terminal for reexec.
 	// The main concern is the nsenter execution before the reexec.
-	// If anythong goes wrong and we mess up with nsenter debugging
+	// If anything goes wrong and we mess up with nsenter debugging
 	// is extremely hard.
 	if unikontainer.Spec.Process.Terminal {
 		ptm, err := pty.Start(reexecCommand)
diff --git a/cmd/urunc/log_forward.go b/cmd/urunc/log_forward.go
@@ -26,7 +26,6 @@ import (
 	"github.com/sirupsen/logrus"
 )
 
-// Spelcheck isues triger
 var msgRegex = regexp.MustCompile(`^([\w\-]+\[\d+\]): (.+)$`)
 
 type StructuredJSONFormatter struct{}
diff --git a/docs/design/index.md b/docs/design/index.md
@@ -20,7 +20,7 @@ In the unikernel context a single-process application runs directly on top of a
 Virtual Machine (VM) or a sandbox. At the same time, in the VM context, every
 VM runs as a process. Subsequently, `urunc` combines these two characteristics
 and treats the VM's process, which executes the unikernel that runs the
-application, as the container's process. This way, `urunc` does not reuire any
+application, as the container's process. This way, `urunc` does not require any
 auxiliary process running alongside the unikernel, maintaining as less overhead
 as possible. Instead `urunc` directly manages the application running in the
 unikernel through the VMM or the sandbox monitor. Moreover, `urunc` does not
@@ -61,7 +61,7 @@ or the unikernel and the aforementioned metadata which dictate how the unikernel
 should be run. The metadata can be passed to `urunc` either in the form of
 [annotations](https://github.com/opencontainers/runtime-spec/blob/main/config.md#annotations)
 or as a specific file in the container's rootfs. For a detailed explanation and
-an up-to-date list of the currently supported annotations take alook at the
+an up-to-date list of the currently supported annotations take a look at the
 [packaging unikernels page](../package/#annotations).
 
 Although `urunc`-formatted unikernel images are not designed to be executed by
diff --git a/docs/developer-guide/Code-of-Conduct.md b/docs/developer-guide/Code-of-Conduct.md
@@ -4,5 +4,5 @@ title: "Code of Conduct"
 description: "Code of Conduct"
 ---
 
-All maintainers and communicty members of `urunc` must abide the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
+All maintainers and community members of `urunc` must abide the [CNCF Code of Conduct](https://github.com/cncf/foundation/blob/main/code-of-conduct.md).
 
diff --git a/docs/developer-guide/governance.md b/docs/developer-guide/governance.md
@@ -75,7 +75,7 @@ is the governing body for the project.
 To become a Maintainer you need to demonstrate the following:
 
   * commitment to the project:
-    * actively participate in mettings, discussions, contributions, code and
+    * actively participate in meetings, discussions, contributions, code and
       documentation reviews for at least 6 months,
     * perform reviews for at least 3 non-trivial pull requests,
     * contribute 3 non-trivial pull requests and have them merged,
diff --git a/docs/developer-guide/security.md b/docs/developer-guide/security.md
@@ -31,7 +31,7 @@ address delivers your message securely to all maintainers.
 
 ### Vulnerability handling process
 
-Upon the receival of a vulnerability report, the following process will take place:
+Upon the receipt of a vulnerability report, the following process will take place:
 
 - the `urunc` maintainers will acknowledge and analyze the report within 48
   hours
diff --git a/docs/developer-guide/timestamps.md b/docs/developer-guide/timestamps.md
@@ -92,7 +92,7 @@ $ cat /tmp/urunc.zlog | grep TS
 
 > Note: the timestamp destination (`/tmp/urunc.zlog`) is hardcoded for the time being.
 
-## Gethering the timestamps
+## Gathering the timestamps
 
 There are 3 Python utilities inside the `script/performance` directory to help gather the timestamps.
 
diff --git a/docs/hypervisor-support.md b/docs/hypervisor-support.md
@@ -230,7 +230,7 @@ seccomp filter allowing only seven system calls. The unikernel running on top of
 interacts with this monitor through a similar interface with
 [Solo5-hvt](https://github.com/Solo5/solo5), facilitating network and block
 storage I/O. [Solo5-spt](https://github.com/Solo5/solo5) can provide extremely
-fast intantiation times, very small overhead, along with performant execution.
+fast instantiation times, very small overhead, along with performant execution.
 
 #### Installing Solo5-spt
 
diff --git a/docs/index.md b/docs/index.md
@@ -14,7 +14,7 @@ For the above purpose `urunc` acts as any other OCI runtime. The main
 difference of `urunc` with other container runtimes is that instead of
 spawning a simple process, it uses a Virtual Machine Monitor (VMM) or a sandbox
 monitor to run the unikernel. It is important to note that `urunc` does not
-require any particular software running alongise the user's application inside
+require any particular software running alongside the user's application inside
 or outside the unikernel. As a result, `urunc` is able to support any unikernel
 framework or similar technologies, while maintaining as low overhead as
 possible.
@@ -31,7 +31,7 @@ possible.
 
 Unikernels are well known as a good fit for a variety of use cases, such as:
 
-- Microservices: The lightweight and almost deminished *OS noise* of unikernels
+- Microservices: The lightweight and almost diminished *OS noise* of unikernels
   can significantly improve the execution of applications, making unikernels an
   attractive fit for microservices.
 - Serverless and FaaS: The extremely fast instantiation time of unikernels
diff --git a/pkg/unikontainers/storage.go b/pkg/unikontainers/storage.go
@@ -28,7 +28,6 @@ import (
 
 var ErrMountpoint = errors.New("no FS is mounted in this mountpoint")
 
-// Inject typo just to verfiy
 // RootFs contains information regarding a mount
 type RootFs struct {
 	Path   string // The path of the root file system.
diff --git a/pkg/unikontainers/unikernels/rumprun.go b/pkg/unikontainers/unikernels/rumprun.go
@@ -161,7 +161,7 @@ func (r *Rumprun) MonitorCli(_ string) string {
 func (r *Rumprun) Init(data UnikernelParams) error {
 	// if EthDeviceMask is empty, there is no network support
 	if data.EthDeviceMask != "" {
-		// FIXME: in the case of rumprun & k8s, we need to identofy
+		// FIXME: in the case of rumprun & k8s, we need to identify
 		// the reason that networking is not working properly.
 		// One reason could be that the gw is in different subnet
 		// than the IP of the unikernel.
diff --git a/tests/e2e/common.go b/tests/e2e/common.go
@@ -47,7 +47,7 @@ type testTool interface {
 	inspectPAndGet(string) (string, error)
 }
 
-var errToolDoesNotSupport = errors.New("Operarion not support")
+var errToolDoesNotSupport = errors.New("Operation not support")
 
 func commonNewContainerCmd(a containerTestArgs) string {
 	cmdBase := "--runtime io.containerd.urunc.v2 "
diff --git a/tests/e2e/test_functions.go b/tests/e2e/test_functions.go
@@ -75,18 +75,18 @@ func userGroupTest(tool testTool) error {
 	groups := strings.Split(strings.TrimSpace(groupString[1]), " ")
 
 	if uid != args.UID {
-		return fmt.Errorf("Mismmatch in uid. Got: %d should be %d", uid, args.UID)
+		return fmt.Errorf("Mismatch in uid. Got: %d should be %d", uid, args.UID)
 	}
 
 	if gid != args.GID {
-		return fmt.Errorf("Mismmatch in gid. Got: %d should be %d", gid, args.GID)
+		return fmt.Errorf("Mismatch in gid. Got: %d should be %d", gid, args.GID)
 	}
 
 	lenag := len(args.Groups)
 	if lenag > 0 {
 		lenpg := len(groups)
 		if lenpg != (lenag + 1) {
-			return fmt.Errorf("Mismmatch in groups length. Got: %d should be %d",
+			return fmt.Errorf("Mismatch in groups length. Got: %d should be %d",
 				lenpg, lenag+1)
 		}
 		for _, groupid := range args.Groups {
@@ -130,7 +130,7 @@ func seccompTest(tool testTool) error {
 
 func namespaceTest(tool testTool) error {
 	// We need to retrieve the container's config, in order to get
-	// the neamspaces that the container should have joined.
+	// the namespaces that the container should have joined.
 	containerID := tool.getContainerID()
 	// Try /run/containerd/io.containerd.runtime.v2.task/default/containerID first
 	configPath := filepath.Join("/var/run/containerd/io.containerd.runtime.v2.task/default/", containerID, "/config.json")
@@ -268,7 +268,7 @@ func httpStaticNetTest(tool testTool) (err error) {
 	defer func() {
 		tempErr := netns.Set(origns)
 		if tempErr != nil {
-			err = fmt.Errorf("Failed to revert to default network nampespace: %v", err)
+			err = fmt.Errorf("Failed to revert to default network namespace: %v", err)
 		}
 	}()
 	ifaces, err := net.Interfaces()

Original file line number	Diff line number	Diff line change
`@@ -26,7 +26,6 @@ import (`
`26`	`26`	`"github.com/sirupsen/logrus"`
`27`	`27`	`)`
`28`	`28`
`29`		`-// Spelcheck isues triger`
`30`	`29`	var msgRegex = regexp.MustCompile(`^([\w\-]+\[\d+\]): (.+)$`)
`31`	`30`
`32`	`31`	`type StructuredJSONFormatter struct{}`