Docs: Clarify stride for upcoming token classification pipeline
I just tried out the upcoming `stride` option for token classification pipelines (#21771, very useful!) without being familiar with the non-standard use of `stride` in the underlying tokenizer settings.

I think it would be helpful to also explain in the pipelines API documentation that the `stride` parameter sets the overlap and not the stride. I thought it was the stride and spent a while trying to figure out why the performance was so abysmal.
Sounds like something missing indeed. Would you like to open a PR with such documentation?<|||||>I'm not confident that I could hit the style that you're looking for in your docs, especially given the history behind the naming.

It might be a lot simpler to document if `stride` were renamed, though, would you potentially consider renaming it for `TokenClassificationPipeline`?<|||||>cc @Narsil what do you think?<|||||>Indeed the name `stride` is not particularly well chosen, my oversight on this.

Seems we have the same thing in question answering: https://github.com/huggingface/transformers/blob/main/src/transformers/pipelines/question_answering.py#L361
And here: https://github.com/huggingface/transformers/blob/main/src/transformers/pipelines/automatic_speech_recognition.py#L169

I think controlling the overlap is much better in general since when you sending text (or audio) you have no idea of the max_length of the truncated texts, so controlling real stride would mean requiring arithmetic with that maximum size. (stride = tokenizer,model_max_length - overlap)

Given the history of that parameter I'm not sure what we should do. Documenting it better would be a start.

Renaming would warrant a rename if those 2 other pipelines. My current off the bat feeling is that we simply shouldn't. It's ok if it just means something different than for the convolution operator.<|||||>For the name `stride`, I choose the same as mentioned for tokenizers: 
stride (int, optional) — The length of the previous first sequence to be included in the overflowing sequence

This parameter is directly passed through the tokenizer in the `preprocess()` method. We can change the name of course, but to keep consistency throughout the documentation, it's better to change all names related to `stride` which in fact refer to the number of overlapping tokens from the previous chunk/sequence.