Pawn, Actor, PlayerController - not exactly sure why there are 3, and I would like the differences to be spelled out in the documentation (is the controller just physics? Nothing more?). From previous UE versions I think Pawn is specifically a player or NPC Actor instance, so that makes sense. It’s a gameplay context term not engine, but I think that’s actually better like it is. Now that I’m a bit familiar with the whole Epic flavor of design I don’t exactly want to change anything.
In the FirstPerson sample, I didn’t easily learn that the Blueprint functionality extends the c++ class - it’s an of presenting the key points of what happens and how, I think.
Local/World space is again something that would be better explained visually for brevity. Havok does a great job of using the right image when introducing skeletal local/world spaces in their documentation (the Biped picture). For non-mathematical readers, bone pose local/world space can intimidating, but that picture had me understand it in a snap. Unity has picture: ://docs.unity3d/ScriptReference/Vector3.Cross.html