Generalised/tense-corrected the example

[goyalyashpal]

What is it?

• Bugfix (user facing)
• Feature (user facing)
• Codebase improvement (dev facing)
• Meta improvement to the project (dev facing)

Description of the changes in your PR

• Updated the tense of the example so that it aligns with the general case it's intended to point to. it helps to avoid misunderstanding about current distribution status.

Fixes the following issue(s)

• Fixes #

APK testing

On the website the APK can be found by going to the "Checks" tab below the title and then on "artifacts" on the right.

Due diligence

• I read the contribution guidelines.

[opusforlife2]

The text in brackets is a hypothetical example of something that might happen every now and then, not a reference to the one particular incident you're thinking of where Newpipe was stuck on an old version on F-Droid. So the current version is correct and there is no change needed.

But thanks for the thought, Yash. ;)

[goyalyashpal]

/close ?
edit: oh wait no

[triallax]

LGTM. Not merging right now to know @opusforlife2's and possibly others' opinions.

[goyalyashpal]

LGTM ?

[triallax]

It means "looks good to me."

[opusforlife2]

There's also the classic "LGTM to me!".

@yashpalgoyal1304 Please change the title and body, as this PR is now doing something completely different.

@mhmdanas It's asking me to approve and run the workflow. Is it okay to do that at any point or is there something to look out for?

Feel free to merge this after he changes the title and body.

[goyalyashpal]

change t & b

done

[triallax]

Thanks!