From 58da1f9f5e58c2f4a14e311c20df70a505b15f2b Mon Sep 17 00:00:00 2001 From: Adrien Plazas Date: Mon, 10 Feb 2025 10:04:22 +0100 Subject: [PATCH] doc/source/arch_caches.rst: Fix typos Signed-off-by: Adrien Plazas --- doc/source/arch_caches.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/arch_caches.rst b/doc/source/arch_caches.rst index 6a3e7e48a..c00437872 100644 --- a/doc/source/arch_caches.rst +++ b/doc/source/arch_caches.rst @@ -30,11 +30,11 @@ The majority of data is stored in Content Addressable Storage or CAS, which indexes stored files by the SHA256 hash of their contents. This allows for a flat file structure as well as any repeated data to be shared across a CAS. In order to store directory structures BuildStream's CAS uses `protocol buffers`_ -for storing directory and file information as defined in Googles `REAPI`_. +for storing directory and file information as defined in Google's `REAPI`_. The data itself is stored in CAS which is defined by the `remote execution protocol`_, and BuildStream also uses the `remote asset protocol`_ in order to address stored -content using symbolic labesl, such as :ref:`artifact names ` for +content using symbolic labels, such as :ref:`artifact names ` for artifacts.