Skip to content

Commit

Permalink
fix a word
Browse files Browse the repository at this point in the history
random thing I noticed reading the docs

Signed-off-by: Rafael <[email protected]>
  • Loading branch information
rgarcia committed Jan 7, 2025
1 parent 38bf8ca commit b8c943d
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 9 deletions.
8 changes: 4 additions & 4 deletions content/docs/cli/building.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,21 +6,21 @@ description: |
applications from scratch or converting existing applications to a unikernel.
---

Before beginning, it's important to famliarize yourself with [the general
Before beginning, it's important to familiarize yourself with [the general
understanding of what a unikernel is](/docs/concepts#introduction-to-unikernels)
and [Unikraft's underlying build process](/docs/concepts/build-process). This
can help you better troubleshoot issues may run into when building your
can help you better troubleshoot issues you may run into when building your
application as a unikernel.

There are several different ways you can build a unikernel using Unikraft and
with `kraft`. Fundementally, there are two ways in which a unikernel can be
with `kraft`. Fundamentally, there are two ways in which a unikernel can be
used:

1. To compile code natively against the Unikraft library Operating System (which
generally has better performance). In this first scenario, the user-level
application code is written in a compile-time language, like C, Go or Rust.

2. To use a "loader" which accepts arbirary user code or binaries which is
2. To use a "loader" which accepts arbitrary user code or binaries which is
executed on top of an existing, pre-built unikernel. In this second
scenario, either the user program is built using an interpreted language such
as Python or JavaScript, or, it is a pre-compiled Linux userspace binary.
Expand Down
10 changes: 5 additions & 5 deletions content/docs/cli/packaging.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ kraft pkg update
src="/asciinema/kraft-pkg-update.cast"
/>

This will locally store information locally about packages and library
This will store information locally about packages and library
components. [This location on-disk](#) and [the remote location of the
component locations](#) can be configured to yours needs.

Expand All @@ -53,14 +53,14 @@ occurring.
Unikraft ships (and `kraft` allows you to ship) packages of different component
types. A component is a building block, and ultimately a code base, repository
or distributable archive or binary, which is used within the Unikraft ecosystem.
Components are one of 5 unique types:
Components are one of five unique types:

| Type | Description |
|--------|-------------|
| `core` | A repository containing the [Unikraft core codebase](https://github.com/unikraft/unikraft) which consists of a Make and KConfig-based build system. The Unikraft core provides the glue for stiching other components as well as your application together. |
| `core` | A repository containing the [Unikraft core codebase](https://github.com/unikraft/unikraft) which consists of a Make and KConfig-based build system. The Unikraft core provides the glue for stitching other components as well as your application together. |
| `arch` | The component that defines behavior and hardware interactions specific to the target architecture. |
| `plat` | A repository containing code that defines the interaction with the underlying hardware, depending on whether a hypervisor is present or not, and which hypervisor is present. |
| `lib` | A repository containing a [Unikraft external library](https://unikraft.org/docs/concepts/#unikraft-libraries), that defines an user-space functionality. |
| `lib` | A repository containing a [Unikraft external library](https://unikraft.org/docs/concepts/#unikraft-libraries), that defines a user-space functionality. |
| `app` | The final component type is that of a fully functioning unikernel. The `app` component defines the use of the `core`, a `arch` and `plat` combination, as well as a list of `lib`s. |


Expand Down Expand Up @@ -97,7 +97,7 @@ registry, simply [add it as a source](#sourcing-additional-packages).

You can configure different backends for OCI images, the default is
directory-based and will store the artifacts locally on disk. Alternatively,
you can use [containerd](https://https://containerd.io/) as a backend by setting
you can use [containerd](https://containerd.io/) as a backend by setting
the [`containerd_addr` to the daemon socket in the global
settings](/docs/cli/options).

Expand Down

0 comments on commit b8c943d

Please sign in to comment.