Editorial tweaks to doc.ipfs.tech/concepts/ipni page #2238
Merged
+19
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
🚀 Build Preview on IPFS ready
|
someguy is a caching proxy for routing lookups (read path), index-provider is a sidecar for publishing (write path)
- break up dense paragraphs - simplify sentence structure - clarify DHT re-announcement timing - reword benefits section for clarity
- "outside of and independent from" → "outside and independent of" - add archivers, benchmarked, realtime to pln-ignore.txt
lidel
approved these changes
Jan 21, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe your changes
Just a slight shift in attitude to better explain IPNI to someone hearing about it for the first time.
Files changed
/docs/concepts/ipni.md
What issue(s) does this address?
Just laying the groundwork for a less contentious conversion about IPNI going forward, in light of recent study of the Content Routing WG and related IPIPs.
Does this update depend on any other PRs?
Nope
Checklist before requesting a review
Checklist before merging