The problem with most visual programming languages is that they don't transition well to written languages, which you start to pine for after getting sick of dragging the output of one module to the input of another for the 300th time. You want this just for laziness/productivity reasons, and it also happens to be a good way to get her motivated to learn English faster.
This is going to feel fun for a while and is an easy way to start, because it's partly like cheating, and when you push numbers to ridiculous extents, it can even really change the nature of gameplay sometimes.
But there's going to come a point where she's sick of being limited to changing surface stuff, and she's going to want to change behaviours, so she's gonna need to look inside of that Badguy.js file attached to the bad guy that she put the pink hat on for "public float healthPoints;" to see what happens to the "Health Points" mentioned in the inspector for the bad guy class so she can come up with a special weapon that cuts the hit points in half, or that heals the baddie up slowly, or that makes the baddie pinker, or whatever she wants to do.
Lo and behold. She's coding.
Unity is made in Copenhagen, so I'm sure Danish docs are possible, but I don't know much about where they'd be. I think if you want to code, tho, you'd better get used to English. English won that war.