From f668f509758f848d17ab824b363bb35bca832740 Mon Sep 17 00:00:00 2001 From: qoog Date: Sun, 9 Mar 2025 13:03:48 +0300 Subject: [PATCH] docs: Correct usage of "API" in documentation --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9e1fdfc..8cd9135 100644 --- a/README.md +++ b/README.md @@ -18,9 +18,9 @@ either `file` or `s3`. The `s3` backend will also work with (for example) Google Cloud Storage buckets (instructions [here](https://medium.com/google-cloud/using-google-cloud-storage-with-minio-object-storage-c994fe4aab6b)). ### Data Validity -Currently, the archiver and api do not validate the beacon node's data. Therefore, it's important to either trust the +Currently, the archiver and API do not validate the beacon node's data. Therefore, it's important to either trust the Beacon node, or validate the data in the client. There is an open [issue](https://github.com/base/blob-archiver/issues/4) -to add data validation to the archiver and api. +to add data validation to the archiver and API. ### Development The `Makefile` contains a number of commands for development: