Skip to content

Fix wording #13186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 20, 2020
Merged

Fix wording #13186

merged 1 commit into from
Feb 20, 2020

Conversation

jschaedl
Copy link
Contributor

No description provided.

@@ -525,7 +525,7 @@ Troubleshooting
The ``@group time-sensitive`` and ``@group dns-sensitive`` annotations work
"by convention" and assume that the namespace of the tested class can be
obtained just by removing the ``Tests\`` part from the test namespace. I.e.
that if the your test case fully-qualified class name (FQCN) is
if your test case's fully-qualified class name (FQCN) is
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the 's, it's only used for real person, not thing.

@OskarStark
Copy link
Contributor

Thank you, I addressed @HeahDude's comment while merging 👍

@OskarStark OskarStark merged commit 91713a3 into symfony:3.4 Feb 20, 2020
OskarStark added a commit that referenced this pull request Feb 20, 2020
OskarStark added a commit to OskarStark/symfony-docs that referenced this pull request Feb 20, 2020
* 3.4:
  minor. refs symfony#13186
  [Security] clarified the encoding with memory providers
  Fix wording
OskarStark added a commit that referenced this pull request Feb 20, 2020
* 4.4:
  minor. refs #13186
  [Security] clarified the encoding with memory providers
  Fix wording
OskarStark added a commit that referenced this pull request Feb 20, 2020
* 5.0:
  minor. refs #13186
  [Security] clarified the encoding with memory providers
  Fix wording
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants