Loading policy/tpa-rfc-15-email-services.md +4 −4 Original line number Diff line number Diff line Loading @@ -457,11 +457,11 @@ requirements with the current infrastructure. Here we collect a few "personas" and try to see how the changes will affect them. > I have taken the liberty of creating mostly fictitious personas, but > they are somewhat based in real-life people. I do not mean to > We have taken the liberty of creating mostly fictitious personas, but > they are somewhat based in real-life people. We do not mean to > offend, any similarity that might seem offensive is an honest > mistake on my part which I will be happy to correct. Also note that > I might have mixed up people together, or forgot some. If your use > mistake on our part which we will be happy to correct. Also note that > we might have mixed up people together, or forgot some. If your use > case is not mentioned here, please, please do mention it. We don't > need to have *exactly* you here, but all your current use cases > should be covered by one or many personas. Loading Loading
policy/tpa-rfc-15-email-services.md +4 −4 Original line number Diff line number Diff line Loading @@ -457,11 +457,11 @@ requirements with the current infrastructure. Here we collect a few "personas" and try to see how the changes will affect them. > I have taken the liberty of creating mostly fictitious personas, but > they are somewhat based in real-life people. I do not mean to > We have taken the liberty of creating mostly fictitious personas, but > they are somewhat based in real-life people. We do not mean to > offend, any similarity that might seem offensive is an honest > mistake on my part which I will be happy to correct. Also note that > I might have mixed up people together, or forgot some. If your use > mistake on our part which we will be happy to correct. Also note that > we might have mixed up people together, or forgot some. If your use > case is not mentioned here, please, please do mention it. We don't > need to have *exactly* you here, but all your current use cases > should be covered by one or many personas. Loading