Already done, though Google Forms compress the image, which makes it harder to read.
As for 3, please paraphrase it.
I just saw that – I missed that edit.
The issue is that it’s slightly suggestive – something that should be avoided. Maybe something like the following could be better?
Please have a look at the pictures of the “Answer Buttons” and “True Retention” table/chart in the question above. Which of the following options do you most agree with?
“Answer Buttons” chart should be removed.
“True Retention” table should be removed.
Both should be removed.
Both should be combined.
None should be removed.
Done 
Looks good to me.
Alright, I posted it on r/Anki and in the Anki Discord server. Link to the summary of results: "True Retention" table and "Answer Buttons" chart
why not just leave the answer graph but remove the %s from the labels
people who want to use it as a count of presses still get it and the ability to confuse it for any sort of real metric goes away
(no ones gonna be crunching those numbers themselves when theres readily available %s next to it)
@A_Blokee Idk who to ask, so I’ll ask you 
Since turning on FSRS my retention has been lower than 90% even though it’s set at 0.90 : r/Anki
A post where the user looks at Answer Buttons and not at the True Retention table.
I really hope this gets merged: Add help modal to TR table by GithubAnon0000 · Pull Request #3874 · ankitects/anki · GitHub
I set it to draft for now because @llama pointed out that on:mount should be added back. I removed it because eslint would fail the test otherwise (due to unused code) which means the code I already had wasn’t complete.
I didn’t look into it yet, though. Once the on:mount code has been pushed / added into the PR, I’ll mark it as “ready for review”.
If we can’t have the stats page share one help modal or if it’s not a good idea to then on:mount could be left out. This’ll be the first instance where it’ll only have one heading that’s also the title of the modal, which isn’t a bad thing but looks somewhat weird imo (seeing “True Retention” repeated thrice in a row)
… but again, it wasn’t an issue.
[And it was only 5 weeks after the first release that included the TR table.]
Sure, it wasn’t the main problem, but when someone has the TR table in their own screenshot and still looks at the wrong graph, to me that’s a very clear signal that something needs to be changed.
Please think about it for a moment. The user has the TR table in their own screenshot, yet he still decided to look at Answer Buttons instead. What more proof that the current implementation is confusing do you need?
Maybe that user just doesn’t understand what “true retention” means. I thought retention was quite commonly used in english but maybe a synonym (or brief half-sentence) might make it more obvious.
I also still doubt that having the help modal would have fixed the issue for that user.
You’re still operating from the premise that looking at Answer Buttons is wrong or bad, and anyone who does that is confused. But there doesn’t seem to be any basis for believing that.
It’s also possible that this user is accustomed to using Answer Buttons for this, so they haven’t even looked yet at whatever new-fangled chart got added to Stats in the past few weeks. Not all of us are enthusiastic adopters of new features. [And we’ve all already agreed that the chart was hard to look at in that first release!]
According to your survey results as of today – that might still be about 10% of users. But there’s nothing wrong with that.
