The overall picture is relatively simple, so you can tell what doesn't fit in your head and we can help you. But if you want to understand the algorithms and why they are as they are then it's time to study a lot of mathematics. And that's why it is important to have an introductory page about security, where the big picture can be shown and links for further study can be provided.
I was just pointing out that there was a lot of technical information about the packets, themselves, that was missing, and would be needed to implement this in a hobby OS. It seemed like the article was, to use an analogy, jumping directly to HTML without first describing HTTP, or TCP/IP, or Ethernet.
I've split the page into 3. I will also work on adding more details about the TLS packets.
Thanks. I think that works much better. I added a few enums and header structs as well. I'll try to add some more when I get some free time.
But the best way to understand how they are formed is to examine at a TLS communication using Wireshark.
Please don't put that on the wiki page