I think it is a bit light on the module/unit system.
What would you like to add specifically?
And on string types (compared to C) and why they are faster to evaluate and have some distinct advantages over just only zero terminated strings.. I noticed that when answering a different question and I am now reading it more thoroughly.
This I would like to keep simple. For programmers coming from Java or C# or modern C++ (with std::string) or PHP or Python or..., it's not news that using strings is easy, and they can be just concatenated with an operator, and you don't need to worry about memory management. I think that only for programmers that never used anything else than bare C, such strings are "news"
So I would like to keep string "description" to a short comment "strings are automatically managed". Numerous examples show that we simply add strings, and pass them around to/from functions. I feel that the description of inner-workings (reference counting, copy on write etc.), are better left for a proper language manual like
http://freepascal.org/docs-html/current/ref/refsu10.html . Same for alternatives (ShortString, WideString) -- for simple string manipulation, using {$H+} and "string" should suffice, IMHO.
In unrelated news, stuff that I'd still like to add is
- (maybe) Basic RTTI example.
- Example of streaming of the published properties - simple read/write example of a custom class.