From 159d64e4ed254aafbb48c2d43e47c8510b26c520 Mon Sep 17 00:00:00 2001
From: Sam Leffler <sleffler@google.com>
Date: Fri, 19 Aug 2022 07:39:34 -0700
Subject: [PATCH] README.md: fixups

Change-Id: I9dc18155328360922919224455f83c5762789c6c
GitOrigin-RevId: 3fc7b8106de1eaac2601b1f9903951017dcfd01b
---
 README.md | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 34a9f77..1064790 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,10 @@ the seL4 source trees since it contains code not intended to go to upstream
 seL4.
 
 This uses the [standard CAmkES build system](https://docs.sel4.systems/projects/camkes/manual.html#running-a-simple-example)
-by symlinking CMakeLists.txt. It also symlinks settings.cmake, and so retains
+by symlinking CMakeLists.txt and assumes
+the [CAmkES dependencies](https://docs.sel4.systems/projects/buildsystem/host-dependencies.html#camkes-build-dependencies)
+are already installed.
+It also symlinks settings.cmake, and so retains
 the notion of "apps," which enables the build system to switch which assembly
 it builds using the CAMKES\_APP CMake cache value. KataOS just has one app,
 *system*.
@@ -45,7 +48,7 @@ To use crates from Sparrow you can reference them from a local repository or
 directly from GitHub using git; e.g. in a Config.toml:
 ```
 kata-os-common = { path = "../system/components/kata-os-common" }
-kata-os-common = { git = "https://github.com/AmbiML/sparrow/kata" }
+kata-os-common = { git = "https://github.com/AmbiML/sparrow-kata" }
 ```
 NB: the git usage depends on cargo's support for searching for a crate
 named "kata-os-common" in the kata repo.