I can respond a little, but please also heed the advice coming from others. I think maybe what is needed from you is a circular, go study an item or two on your list, and, best of all, is when you can come back in with a specific question, and describing where you've gotten snagged on some detail.
Proceeding that way, you can keep your FOCUS; meanwhile you can, periodically, bring your questions.
Especially details, about where you've gotten stuck.
No such thing as a stupid question, according to variable skill level.
Anyway, I think the coding term 'In-line' refers to little (usually brief) lines of code, that allow quick, simple, and very direct action. Often that's just one single action that, is either doing very fast/brief, or doing something the high level language cannot.
Maybe not some simple thing, like 'bit-shift', but more like a 'Force Parity Error' diagnostic command, that isn't implemented in the actual host language.
Probability that the above is correct,...maybe 57%.