-
Notifications
You must be signed in to change notification settings - Fork 5
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
Translation of /testing/index.md page. #255
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for your contribution @antoheri ❤️ I commented a couple of tiny typos and a few proposals to improve a little bit some sentences.
guides/testing/index.md
Outdated
@@ -1,78 +1,78 @@ | |||
Ember gives you **the power to write tests and be productive from day one**. You can be confident that your app will be correct today and years from now. A question remains: _How_ should you write tests? | |||
Ember vous donne **la puissance d'écrire des tests et d'être productif dès le premier jour**. Vous pouvez être sûr que votre application fonctionnera correctement aujourd'hui et dans des années. Une question demeure : Comment devriez-vous écrire des tests ? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Better phrasing:
Ember vous donne **la puissance d'écrire des tests et d'être productif dès le premier jour**. Vous pouvez être sûr que votre application fonctionnera correctement aujourd'hui et dans des années. Une question demeure : Comment devriez-vous écrire des tests ? | |
Ember vous donne **la puissance d'écrire des tests et d'être productif dès le premier jour**. Vous pouvez être sûr que votre application fonctionnera correctement aujourd'hui et dans les années à venir. Une question demeure : Comment devriez-vous écrire des tests ? |
Thank's for the review and the suggestions ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One change from the previous review was forgotten.
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: Marine Dunstetter <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
Co-authored-by: MrChocolatine <[email protected]>
05c76c9
to
97d6b21
Compare
I added the linter and rebased the PR to resolve the conflict with catchup 5.11. |
Fixes #111