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.

首先比较参数文档与教程文档，重点关注其中的说明性文字、示例和链接。当项目在两份文档之间形成了约定的边界，并在不让教程读者依赖频繁链接的情况下减少了过度冗余时，这项工作就完成了。