Thorough coverage does not equal clear and consice coverage. You asked for the editorial feedback.
What's not clear and concise about it? I really need some more context / examples of what you're envisioning the part to look and read like.
Also, while I'm at it, I'd appreciate an example in regards to "why one should chose to run a node and perhaps who should or should not, yet."
reply
Your intro starts with a very fine what, but one must read paragraphs before the why is covered. You may find many, especially those younger than 40 will need read far enough for the why. I read, write, and edit in my work and you had to point it out to me. If you are pointing things out after the fact, consider edits.
Cover the why earlier in your intro.
I have spoken.
reply
Hm. I'll put some further thought towards the structuring, but honestly?
If a few minutes is already too long to get from the detailed "what" to the detailed "why", then it might not be the guide for you.
I'm not saying you're wrong, I simply don't see a way of improving the above as of now, and I kinda fail to see the bigger "why".
reply
The answer to why is who. Who is your audience?
All writers disagree with editors. All writers need editors.
reply
Starters, although I'm trying to portray a pretty complete and thorough picture from the get-go, which might make it more suitable for the already more advanced (knowledgeable) starter.
reply
you're fine for a more intermediate or advanced beginner. They already know the why, so my point is invalid there.
When I say clear and concise I mean for a wider audience. Adding a couple of why statements earlier on opens up the content to some who will stop at paragraph one or two.
Hope you found the discussion helpful.
reply
21 sats \ 1 reply \ @Fabs OP 10 Apr
Can I @ you in the future?
Ah! See, as with anything, it's in the details.
I should've pointed out what kind of audience I'm eyeing, thanks for the clarification, though.
reply