summaryrefslogtreecommitdiff
path: root/doc/tutorial/cross-compiling.md
diff options
context:
space:
mode:
authorPaul Cristian Sarbu <paul.cristian.sarbu@huawei.com>2024-04-12 17:54:11 +0200
committerPaul Cristian Sarbu <paul.cristian.sarbu@huawei.com>2024-04-15 18:05:12 +0200
commit4e2430a102542720337834458d8f20a0f81167db (patch)
tree738d26910bdaff2f474a8b4b74fcf2fe523f8d90 /doc/tutorial/cross-compiling.md
parent0a2a440f0421134f1f741a74c88087a9951462bc (diff)
downloadjustbuild-4e2430a102542720337834458d8f20a0f81167db.tar.gz
tutorial: Consistent formatting and small fixes
Diffstat (limited to 'doc/tutorial/cross-compiling.md')
-rw-r--r--doc/tutorial/cross-compiling.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tutorial/cross-compiling.md b/doc/tutorial/cross-compiling.md
index 60bdd3c5..35946a9b 100644
--- a/doc/tutorial/cross-compiling.md
+++ b/doc/tutorial/cross-compiling.md
@@ -193,7 +193,7 @@ binary, we need to do two things.
- We need to setup remote execution on the correct architecture,
either by buying the appropriate hardware, or by running an emulator.
-- We need to tell `justbuild` on how to reach that endpoint.
+- We need to tell *justbuild* on how to reach that endpoint.
To continue the example, let's say we set up an `arm64` machine,
e.g., a Raspberry Pi, in the local network. On that machine, we can
@@ -201,7 +201,7 @@ simply run a single-node execution service using `just execute`;
note that the `just` binary used there has to be an `arm64` binary,
e.g., obtained by cross compiling.
-The next step is to tell `justbuild` how to reach that machine;
+The next step is to tell *justbuild* how to reach that machine;
as we only want to use it for certain actions we can't simply
set it as (default) remote-execution endpoint (specified by the
`-r` option). Instead we crate a file `dispatch.json`.