Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
minor #31074 minor: the meaning of the data breach was not correct (S…
…imperfit) This PR was squashed before being merged into the 3.4 branch (closes #31074). Discussion ---------- minor: the meaning of the data breach was not correct | Q | A | ------------- | --- | Branch? | 3.4 | Bug fix? | no | New feature? | no <!-- don't forget to update src/**/CHANGELOG.md files --> | BC breaks? | no <!-- see https://symfony.com/bc --> | Deprecations? | no <!-- don't forget to update UPGRADE-*.md and src/**/CHANGELOG.md files --> | Tests pass? | yes <!-- please add some, will be required by reviewers --> | Fixed tickets | none <!-- #-prefixed issue number(s), if any --> | License | MIT | Doc PR | none <!-- required for new features --> <!-- Write a short README entry for your feature/bugfix here (replace this comment block.) This will help people understand your PR and can be used as a start of the Doc PR. Additionally: - Bug fixes must be submitted against the lowest branch where they apply (lowest branches are regularly merged to upper ones so they get the fixes too). - Features and deprecations must be submitted against the master branch. --> It seems that the french translation was wrong as the phrasing suggested that the data breach came from the current application/website. Changing as discussed here: #31053 (comment) Commits ------- 97ac9ba minor: the meaning of the data breach was not correct
- Loading branch information