How to handle redundancy between params doc and tutorial doc

As I said in an earlier PR, my aim is for:

• The parameters doc to be about what the parameters do.
• The tutorial doc to be about what the user can do.

There will necessarily be considerable overlap, both the text and in the examples, but I'd like to avoid excessive redundancy.

I don't want the tutorial to "link out" very often. The tutorial reader is entitled to have the relevant material in-line, not linked to.

I'm thinking about having the parameters doc retain its explanatory text, but link to the specific tutorial section for examples. This would make the parameters doc much shorter -- a Good Thing in itself -- and also make the reader aware of the tutorial doc -- possibly another Good Thing.

I will value opinions.

Empieza comparando la documentación de parámetros con la documentación del tutorial, centrándote en sus textos explicativos, ejemplos y enlaces. El trabajo estará terminado cuando el proyecto tenga un límite acordado entre ambos documentos y se haya reducido la redundancia excesiva sin hacer que los lectores del tutorial dependan de enlaces frecuentes.