No worries. PEPs are intended to act as both a technical specification and an argument for the feature being described. That means that the PEP needs to be written in such a way as to persuade the reader that the feature is worth implementing, without making too many assumptions about how much knowledge the reader might have. If it helps, I tend to assume that I’m writing for someone who’s being asked to implement the proposal - such a person is typically being asked to do a non-trivial amount of work, and doesn’t necessarily have a need for the feature themselves (and may not even understand what the fetaure is for).
It appears that @dstufft is the sponsor for this PEP - if you haven’t done so already, you might want to discuss with him how to frame the arguments the PEP is making.