Skip to content
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

Some small changes for clarity #108

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions exercises/an_important_rule/problem.fr.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,9 +54,9 @@ De nombreuses bibliothèques de promesses essaient de pallier à ce
problème en vous fournissant un gestionnaire `done` pour traiter toute
erreur qui n’aurait pas encore été traitée. La règle d’or est simple :

> Si vous **ne renvoyez pas** de valeur depuis votre promesse vers
> le code appelant, ajouter un gestionnaire `done` en fin de chaîne
> pour vous protéger contre les exceptions non traitées.
*Si vous **ne renvoyez pas** de valeur depuis votre promesse vers
le code appelant, ajouter un gestionnaire `done` en fin de chaîne
pour vous protéger contre les exceptions non traitées.*

Voici un exemple :

Expand Down
4 changes: 2 additions & 2 deletions exercises/an_important_rule/problem.md
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@ Many promise libraries try to ameliorate this problem for you
by providing a `done` handler that simply handles any uncaught
errors. The rule of thumb is this:

> If you are **not** returning a value from your promise to a caller,
> then attach a `done` handler to guard against uncaught exceptions.
*If you are **not** returning a value from your promise to a caller,
then attach a `done` handler to guard against uncaught exceptions.*

An example is shown below:

Expand Down
2 changes: 2 additions & 0 deletions exercises/reject_a_promise/problem.fr.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,8 @@ Pour rappel de la leçon précédente, la méthode `then` d’une promesse prend
deux fonctions de rappel optionnelles : la première est appelée quand la
promesse s’accomplit, la seconde quand elle rejette.

Pour plus de détails à propos des objets `Error`, veuillez consulter la [documentation du MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error)

## Base de travail

```js
Expand Down
2 changes: 2 additions & 0 deletions exercises/reject_a_promise/problem.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,8 @@ As a review from last lesson, a promise's `then` function takes two callbacks:
the first to be called when the promise is fulfilled and the second when the
promise is rejected.

For more details on Error objects, you can check out the [MDN documentation](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Error).

## Boilerplate

```js
Expand Down