I don't think it's a translation issue, rather I get the impression that this has been written by educationalists for educationalists. So the pedagogical section is written using the basic technical language for that field, because the assumption is that the main target audience will be familiar with those terms.
It's a bit like how I might prepare a document for colleagues and a non-technical product owner, and I need to overall contents to be clear enough (and non-technical enough) for the PO to understand, but I also want to put technical details in for my colleagues who understand jargon like "load testing" or whatever else. I don't need to simplify the section on load testing and remove that sort of jargon, because in principle it's not necessary for the PO to precisely understand those details.
So I don't think it's a translation issue, but rather it's not designed to be directly a tutorial for getting started with programming, but rather a tool for teachers to teach lessons on getting started with programming.
It's a bit like how I might prepare a document for colleagues and a non-technical product owner, and I need to overall contents to be clear enough (and non-technical enough) for the PO to understand, but I also want to put technical details in for my colleagues who understand jargon like "load testing" or whatever else. I don't need to simplify the section on load testing and remove that sort of jargon, because in principle it's not necessary for the PO to precisely understand those details.
So I don't think it's a translation issue, but rather it's not designed to be directly a tutorial for getting started with programming, but rather a tool for teachers to teach lessons on getting started with programming.