aljaz/pear-docs
1
0
Fork 0
mirror of https://github.com/aljazceru/pear-docs.git synced 2025-12-17 06:24:24 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix spelling mistakes (#150)

Browse Source
This commit is contained in:
Sean Zellmer
2024-10-22 08:07:06 -05:00
committed by GitHub
parent b4ad921fde
commit c0956c273d
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
howto/share-append-only-databases-with-hyperbee.md
View File

@@ -123,7 +123,7 @@ const bee = new Hyperbee(core, {
valueEncoding: 'utf-8'
})
// wait till the hypercore properties to be intialized
// wait till the hypercore properties to be initialized
await core.ready()
// logging the public key of the hypercore instance
@@ -154,7 +154,7 @@ pear run --dev . -- <SUPPLY KEY HERE>
Query the database by entering a key to lookup into the `bee-reader-app` terminal and hitting return.
Each application has dedicated storage at `Pear.config.storage`. Try logging out `Pear.config.storage` for the `bee-reader-app` and then look at the disk space for that storage path after each query. notice that it's significantly smaller than `writer-storage`! This is because Hyperbee only downloads the Hypercore blocks it needs to satisfy each query, a feature we call **sparse downloading.**
Each application has dedicated storage at `Pear.config.storage`. Try logging out `Pear.config.storage` for the `bee-reader-app` and then look at the disk space for that storage path after each query. Notice that it's significantly smaller than `writer-storage`! This is because Hyperbee only downloads the Hypercore blocks it needs to satisfy each query, a feature we call **sparse downloading.**
Importantly, a Hyperbee is **just** a Hypercore, where the tree nodes are stored as Hypercore blocks.