Change case in repo name

README.md

@@ -20,7 +20,7 @@ This work is funded by the [seL4 Foundation](https://sel4.systems/Foundation/hom
 
 ### Rendered rustdoc
 
-[https://coliasgroup.com/rust-seL4/](https://coliasgroup.com/rust-seL4/)
+[https://coliasgroup.com/rust-sel4/](https://coliasgroup.com/rust-sel4/)
 
 ### Demos
 
@@ -101,8 +101,8 @@ The only requirements for running the tests in this repository are Git, Make, an
 First, clone this repository:
 
 ```
-git clone https://github.com/coliasgroup/rust-seL4
-cd rust-seL4
+git clone https://github.com/coliasgroup/rust-sel4
+cd rust-sel4
 ```
 
 Next, build, run, and enter a Docker container for development:

crates/sel4-capdl-initializer/README.md

@@ -22,7 +22,7 @@ Here is an example of how to build and use this crate. First, independantly of t
 build the initializer and accompanying CLI tool:
 
 ```bash
-url="https://github.com/coliasgroup/rust-seL4"
+url="https://github.com/coliasgroup/rust-sel4"
 
 RUST_TARGET_PATH=$my_rust_target_path \
 SEL4_PREFIX=$my_sel4_prefix \
@@ -64,7 +64,7 @@ independantly of the spec and then adding the spec later, the spec is provided t
 script at compile time via environment variables.
 
 ```bash
-url="https://github.com/coliasgroup/rust-seL4"
+url="https://github.com/coliasgroup/rust-sel4"
 
 RUST_TARGET_PATH=$my_rust_target_path \
 SEL4_PREFIX=$my_sel4_prefix \

crates/sel4-kernel-loader/README.md

@@ -26,7 +26,7 @@ Here is an example of how to build and use this crate. First, independantly of t
 build the loader and accompanying CLI tool:
 
 ```bash
-url="https://github.com/coliasgroup/rust-seL4"
+url="https://github.com/coliasgroup/rust-sel4"
 
 CC=aarch64-linux-gnu-gcc \
 SEL4_PREFIX=$my_sel4_prefix \

crates/sel4-microkit/src/lib.rs

@@ -29,9 +29,9 @@
 //! domains must contain the symbol `__sel4_ipc_buffer_obj`. Furthermore, for protection domains
 //! with memory regions, the `microkit` tool injects the addresses of these memory regions at build
 //! time by patching designated symbols. The
-//! [`*-sel4-microkit{,-minimal}.json`](https://github.com/coliasgroup/rust-seL4/tree/main/support/targets)
-//! `rustc` target specs distributed as part of the [rust-seL4
-//! project](https://github.com/coliasgroup/rust-seL4) provide `__sel4_ipc_buffer_obj`, and the
+//! [`*-sel4-microkit{,-minimal}.json`](https://github.com/coliasgroup/rust-sel4/tree/main/support/targets)
+//! `rustc` target specs distributed as part of the [rust-sel4
+//! project](https://github.com/coliasgroup/rust-sel4) provide `__sel4_ipc_buffer_obj`, and the
 //! [`memory_region_symbol`] macro provides a conveneint way to declare memory region address
 //! symbols.
 //!

hacking/nix/top-level/docs/default.nix

@@ -121,7 +121,7 @@ let
           <div class="markdown-body">
             <h1>
               Rustdoc for
-              <a href="https://github.com/coliasgroup/rust-seL4">
+              <a href="https://github.com/coliasgroup/rust-sel4">
                 seL4 crates
               </a>
             </h1>

hacking/nix/top-level/docs/index.md

@@ -4,7 +4,7 @@ representative combinations. Each entry below provides a consistent view of all
 one such combination.
 
 The rustdoc for each view is generated all at once with one `cargo doc` invocation on the
-[`meta`](https://github.com/coliasgroup/rust-seL4/tree/main/crates/private/meta) crate, whose only
+[`meta`](https://github.com/coliasgroup/rust-sel4/tree/main/crates/private/meta) crate, whose only
 purpose is to depend on and select features for the other crates. Due to a current limitation of
 rustdoc, each view can only include at most one language runtime crate (e.g. `sel4-root-task` or
 `sel4-microkit`).