Commit f90d537
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -85,7 +85,7 @@ You can pass a second function parameter to the `.then` method that will have | |||
| 85 | 85 | the reason why a promise failed in it's first argument. | |
| 86 | 86 | ||
| 87 | 87 | ``` javascript | |
| 88 | - NodeGit.Repository.open(pathToRepo).then(function (sucessfulResult) { | ||
| 88 | + NodeGit.Repository.open(pathToRepo).then(function (successfulResult) { | ||
| 89 | 89 | // This is the first function of the then which contains the successfully | |
| 90 | 90 | // calculated result of the promise | |
| 91 | 91 | }, function (reasonForFailure) { | |
@@ -100,7 +100,7 @@ You can also append a `.catch` to the end of a promise chain which will | |||
| 100 | 100 | receive any promise failure that isn't previously caught | |
| 101 | 101 | ||
| 102 | 102 | ``` javascript | |
| 103 | - NodeGit.Repository.open(pathToRepo).then(function (sucessfulResult) { | ||
| 103 | + NodeGit.Repository.open(pathToRepo).then(function (successfulResult) { | ||
| 104 | 104 | // This is the first function of the then which contains the successfully | |
| 105 | 105 | // calculated result of the promise | |
| 106 | 106 | }) | |
@@ -115,7 +115,7 @@ If you append a `.done` at the end of your chain, you will have any error that | |||
| 115 | 115 | wasn't previously handled by the above 2 methods thrown. | |
| 116 | 116 | ||
| 117 | 117 | ``` javascript | |
| 118 | - NodeGit.Repository.open(pathToRepo).then(function (sucessfulResult) { | ||
| 118 | + NodeGit.Repository.open(pathToRepo).then(function (successfulResult) { | ||
| 119 | 119 | // This is the first function of the then which contains the successfully | |
| 120 | 120 | // calculated result of the promise | |
| 121 | 121 | }) | |
0 commit comments