Based on the skimming through the titles it looks like a quite complete material.
As it looks like after completing this course people should be quite capable to build their own solutions, I would recommend you to cover the security aspect more broadly.
Perhaps cover multiple commonly known attack vectors (and how they are mitigated) and basics of the cryptology.
I would also suggest you (based on the other comment here) to not push Chrome only. It is very important for our liberty to have various actively used browsers.
I'm not sure he's suggesting everyone should only ever use Chrome, but rather heading off "it doesn't work on my system!" complaints that are common with these tutorials. He goes into painstaking detail on exactly which version of Rails, exactly which version of Ruby, and exactly what gems you need to use to make sure the learner is using the same environment as the teacher. Suggesting that everyone use the same browser goes hand in hand with this. If you're a beginner and you run into compatibility issues with your browser, you might be turned off and quit. Making sure everything is the same while you're learning is really just good practice.
As it looks like after completing this course people should be quite capable to build their own solutions, I would recommend you to cover the security aspect more broadly.
Perhaps cover multiple commonly known attack vectors (and how they are mitigated) and basics of the cryptology.
I would also suggest you (based on the other comment here) to not push Chrome only. It is very important for our liberty to have various actively used browsers.