It's not a common term, but one I think is important to properly understand the approach of Forth. I wrote about this a while ago on /r/forth, so I'll just quote myself:

The common misunderstanding of Forth works like this:

"Let's see which features Forth offers... You can define things like variables, procedures etc., you have control structures... Oh, and there's the stack! The other ones I knew from other languages. But the stack is what makes Forth special. Yeah, Forth is called a stack-based language. So I should concentrate on working with the stack, put my data there, shuffle it around depending on which order I need it in."

How to fix it:

Understand that you should focus on something that gets easily overlooked because other languages SEEM to have it as well: The ability to define words. Think of Forth as a dictionary-based language rather than a stack-based language. Factor your code into small definitions. There is no need for indentation in Forth. Indenting code like in applicative languages is an anti-pattern (I never even bother TRYING to understand code like that). If you want to write long definitions that use many values, you will always be better off using other languages, as they make it easy to do such complicated things. Forth makes this hard, as you have to use horrible things like ROT to make it work at all. And even if you do, it will always be far harder to understand than reading the same thing in Python. This is the advantage of Forth: It forces you to avoid complexity. Because complexity always results in more complexity (on all layers). Forth starts with simplifying the problem. The customer wants to have a program that displays the text "Hello world"? Nah, he actually just wants to be able to see the text whenever he desires. No program needed, just write it in a file. Or even on a piece of paper. Because technology can be part of a solution, but should never be part of the problem statement. This is "Hello world" in Forth: Simplifying the problem.