From 686bbc13cbeb00c436e9a28df0a9aab57ebe65aa Mon Sep 17 00:00:00 2001 From: rocksload Date: Sun, 26 Oct 2025 18:20:27 +0800 Subject: [PATCH] chore: fix typo in _docs/README.md Signed-off-by: rocksload --- _docs/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/README.md b/_docs/README.md index fba77bd..17b4a66 100644 --- a/_docs/README.md +++ b/_docs/README.md @@ -17,7 +17,7 @@ In our experience, each p2p blockchain node has more or less these components, e * Team scalability -- with well specified components, it's easy to make sub-teams that work on each component with less coordination overhead. Most cross-team communication is around the interface definition and interpretation. -* Learning curve reduction -- it is not that easy to find a full-fledged blockchain node developer, but narrowing down the area of responsiblities, makes it easier to both find candidates and coach/mentor the right skillset for them. +* Learning curve reduction -- it is not that easy to find a full-fledged blockchain node developer, but narrowing down the area of responsibilities, makes it easier to both find candidates and coach/mentor the right skillset for them. * Innovation and improvements of each layer independently -- for specialized teams for each sub-component, it's easier to find some more improvements or optimizations or innovative approaches than in a team that has to keep everything about the node in the head.