From dbab5d2e9089e62ecdffdca259d0e56ba0f932d6 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Thu, 12 Dec 2024 03:55:23 +0100 Subject: [PATCH] Fix typos (#130) * fix typos * fix typo * fix typos * fix typo * fix typos --- docs/src/getting-started/android-development.md | 4 ++-- docs/src/getting-started/building-the-os.md | 2 +- docs/src/getting-started/rust-android-module.md | 2 +- docs/src/getting-started/rust-in-android.md | 2 +- docs/src/overview/hardware-signing.md | 4 ++-- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/src/getting-started/android-development.md b/docs/src/getting-started/android-development.md index f117d015..09a990aa 100644 --- a/docs/src/getting-started/android-development.md +++ b/docs/src/getting-started/android-development.md @@ -1,8 +1,8 @@ # Android Development Crash Course -Because GrapheneOS (and thus Starknet Phone) is based on android, it is compatiable -with Android native applications. This will be a broad overview on how Android +Because GrapheneOS (and thus Starknet Phone) is based on android, it is compatible +with Android native applications. This will be a broad overview of how Android development is approached in this project. ## Environment/Android Studio setup diff --git a/docs/src/getting-started/building-the-os.md b/docs/src/getting-started/building-the-os.md index db245f05..29dfd450 100644 --- a/docs/src/getting-started/building-the-os.md +++ b/docs/src/getting-started/building-the-os.md @@ -21,7 +21,7 @@ echo 'export PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin' >> ~/.bashrc source ~/.bashrc ``` -More detailed dependiencies and build guide can be found +More detailed dependencies and build guide can be found [here](https://grapheneos.org/build) ## Downloading the source code diff --git a/docs/src/getting-started/rust-android-module.md b/docs/src/getting-started/rust-android-module.md index 673526f3..a8d768bf 100644 --- a/docs/src/getting-started/rust-android-module.md +++ b/docs/src/getting-started/rust-android-module.md @@ -16,7 +16,7 @@ for the build command [Documentaiont](https://developer.android.com/develop/background-work/services) -Main idea: servies are long-running operations in the background that can be accessed mby multiple devices. +Main idea: services are long-running operations in the background that can be accessed by multiple devices. This is what we want for the light client, and is how Ethereum Phone implements their light client. Must be declared in the manifest file: diff --git a/docs/src/getting-started/rust-in-android.md b/docs/src/getting-started/rust-in-android.md index 7440e6d9..3e1c3ea0 100644 --- a/docs/src/getting-started/rust-in-android.md +++ b/docs/src/getting-started/rust-in-android.md @@ -54,7 +54,7 @@ public class RustLib { ## Writing the rust side -We will writing rust code that compiles as C code to match the C header generated +We will write rust code that compiles as C code to match the C header generated when compiling the Java library created in the previous step. Use javac to compile the Java class into a C header. diff --git a/docs/src/overview/hardware-signing.md b/docs/src/overview/hardware-signing.md index 45425666..29248cf3 100644 --- a/docs/src/overview/hardware-signing.md +++ b/docs/src/overview/hardware-signing.md @@ -11,12 +11,12 @@ extracted from the device via the secure keystore system. [Android Keystore Documentation](https://developer.android.com/privacy-and-security/keystore) Some notable features: -- Extraction prevention: key material cannot be extracted from the deivce in case of theft and +- Extraction prevention: key material cannot be extracted from the device in case of theft and cannot be accessed by application processes. - Hardware security module: similar to a Trusted Execution Environment (TEE), but specifically embedded Secure Elements (eSE) or on-SoC secure processing units (iSE) - Key use authorizations: specific authorizations can be set (and cannot be changed) to enforce - key usage to meet certain constraints such as specific algortithms or time intervals. + key usage to meet certain constraints such as specific algorithms or time intervals. ## The Starknet side