From db59c24a25291306ed4f274bd41ae8bef4a2c533 Mon Sep 17 00:00:00 2001
From: chloefeal <188809157+chloefeal@users.noreply.github.com>
Date: Sun, 29 Dec 2024 20:06:18 +0800
Subject: [PATCH 1/2] core: fix typo

Signed-off-by: chloefeal <188809157+chloefeal@users.noreply.github.com>
---
 core/commands/files.go   | 2 +-
 core/coreiface/unixfs.go | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/core/commands/files.go b/core/commands/files.go
index e06833f6f1d..a9c876d78fd 100644
--- a/core/commands/files.go
+++ b/core/commands/files.go
@@ -68,7 +68,7 @@ of consistency guarantees and unbound growth of the directories' in-memory
 caches.  If the daemon is unexpectedly killed before running 'ipfs files
 flush' on the files in question, then data may be lost. This also applies to
 run 'ipfs repo gc' concurrently with '--flush=false' operations. We recommend
-flushing paths reguarly with 'ipfs files flush', specially the folders on
+flushing paths regularly with 'ipfs files flush', specially the folders on
 which many write operations are happening, as a way to clear the directory
 cache, free memory and speed up read operations.`,
 	},
diff --git a/core/coreiface/unixfs.go b/core/coreiface/unixfs.go
index 10371998c20..a8740e2b3ba 100644
--- a/core/coreiface/unixfs.go
+++ b/core/coreiface/unixfs.go
@@ -105,7 +105,7 @@ type UnixfsAPI interface {
 // Iteration stops if the context is canceled or if the iterator yields an
 // error.
 //
-// Exmaple:
+// Example:
 //
 //	for dirEnt, err := LsIter(ctx, ufsAPI, p) {
 //		if err != nil {

From b060072e75bdb6fdca7941149905128e6f296185 Mon Sep 17 00:00:00 2001
From: chloefeal <188809157+chloefeal@users.noreply.github.com>
Date: Sun, 29 Dec 2024 20:06:27 +0800
Subject: [PATCH 2/2] docs: fix typo

Signed-off-by: chloefeal <188809157+chloefeal@users.noreply.github.com>
---
 docs/config.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/config.md b/docs/config.md
index f1a3895f5de..578c35b7bba 100644
--- a/docs/config.md
+++ b/docs/config.md
@@ -643,7 +643,7 @@ are used, so the constant `k` is 7 in the formula.
 Enabling the BloomFilter can provide performance improvements specially when
 responding to many requests for inexistant blocks. It however requires a full
 sweep of all the datastore keys on daemon start. On very large datastores this
-can be a very taxing operation, particulary if the datastore does not support
+can be a very taxing operation, particularly if the datastore does not support
 querying existing keys without reading their values at the same time (blocks).
 
 Default: `0` (disabled)
@@ -2610,7 +2610,7 @@ Pebble is a LevelDB/RocksDB inspired key-value store focused on performance and
 You should use this datastore if:
 
 - You need a datastore that is focused on performance.
-- You need a datastore that is good for multi-terrabyte data sets.
+- You need a datastore that is good for multi-terabyte data sets.
 - You need reliability by default, but may choose to disable WAL for maximum performance when reliability is not critical.
 - You want a datastore that does not need GC cycles and does not use more space than necessary
 - You want a datastore that does not take several minutes to start with large repositories