Documentation should be changed to avoid "pattern.en" as a module name

[glarchev]

It looks like some of the examples in the documentation use "pattern.en" as a module name -- it appears that it should actually be "pattern.text.en" instead.

[verhoevenben]

No, all language modules were designed by the developers to work as a module on their own (so pattern.en or pattern.it, …) for ease of use, I suppose.
For efficiency of the code, they gathered all language modules under the module ‘text’.

Op 30-nov.-2015, om 23:54 heeft glarchev notifications@github.com het volgende geschreven:

It looks like some of the examples in the documentation use "pattern.en" as a module name -- it appears that it should actually be "pattern.text.en" instead.

—
Reply to this email directly or view it on GitHub #136.

[glarchev]

Since all the language modules are nested under "text", I think it's more confusing to refer to them as just "pattern.en". Although it appears to work, my IDE (PyDev) complains about unresolved import.