You bring up some valid issues, but I think you're missing the point of the guide: To be friendly. It has a few parts that could use some editing but overall it feels friendly and interactive. Some of the changes you suggest make it seem cold and boring, which (to me at least) would be a reason to put it down and never pick it back up.
> Learning HTML and CSS is hard, but it doesn’t have to be.
That's a great start. It's friendly and it doesn't have unnecessary words in it. It's actually quite powerful.
There's a fine line between being friendly and starting to babble.
I am noob, not stupid.
Edit: typo
I think in general someone this new to programming concepts would probably want something a little slower. Once you get the main concepts down for programming then you can speed up, but the abstract thinking is hard for a lot of people to wrap their head around at first.
For speech, the speaker sets the pace, so the challenge of accessibility is actually twofold: the speaker needs to both be clear and not too fast (or too "efficient").
In text, it's the opposite: the reader sets the pace, so more efficient writing will make reading (at whatever pace) less taxing.
It's all a balancing act of course. Like you said, has to be both clear and fast.
1. It took me probably 30 seconds to understand that the text blocks on the start page are summaries of what's in every chapter. Try to read this without knowing that this website is an online book:
> The purpose of HTML, CSS, and JavaScript, the difference between frameworks and languages, and finding your way around a basic website project with Atom.
This doesn't make any sense if you don't know that it describes a chapter in a book.
2. Simplify sentences. Cut adjectives. Shorten. It reads academic. Examples:
> Our goal is to make it as easy as possible for complete beginners to become professional web developers, so if you’ve never written a line of HTML or CSS, but you’re contemplating a career shift, grab a cup of coffee, take a seat, and let’s get to work.
This is a single sentence. It's hard to understand. Your readers aren't all native Americans. This could be turned into:
-> This guide helps you to become a professional web developer, even if you've never written a single line of HTML or CSS.
> They’re very closely related, but they’re also designed for very specific tasks. Understanding how they interact will go a long way towards becoming a web developer.
Ctrl + F "very": Too often.
A good editor might reduce the text by 25-50%. My secret tip is the Material Design Writing guide [1]. It shows how to write for apps. With apps, the user needs to get a task done as fast and efficient as possible. Write that way.
[1] https://material.io/guidelines/style/writing.html