Skip to content

Commit 18cb392

Browse files
committed
fix: value check errors
1 parent d26c2f1 commit 18cb392

File tree

2 files changed

+4
-1
lines changed

2 files changed

+4
-1
lines changed

.github/styles/pln-ignore.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -130,6 +130,7 @@ markdownlint
130130
merkle
131131
merklizing
132132
merkleizing
133+
merkleization
133134
metadata('s)
134135
metamask
135136
minimalistic
@@ -142,6 +143,7 @@ multiaddrs
142143
multibase
143144
multicast
144145
multicodec
146+
multicodecs
145147
multicodec(s)
146148
multiformats
147149
multihash
@@ -217,6 +219,7 @@ testground
217219
testnet
218220
toolkits
219221
trustlessly
222+
trustlessness
220223
uncensorable
221224
undialable
222225
uniswap

docs/how-to/ipfs-in-web-apps.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ This guide has covered the essential aspects of using IPFS in web applications:
119119

120120
When building web applications with IPFS, remember these key takeaways:
121121

122-
1. Use client-side merkleization (addressing) when onboarding new data to IPFS, but rely on pinning services or IPFS nodes for providing data.
122+
1. Use client-side merkleization (addressing) when adding new data to IPFS, but rely on pinning services or IPFS nodes for providing data.
123123
1. Be mindful of CID determinism when working with files and structured data.
124124
1. Consider using CAR files where possible for storage and transport of content-addressed data.
125125
1. Use Verified Fetch for simple retrieval or Helia for more complex IPFS interactions.

0 commit comments

Comments
 (0)