diff --git a/src/content/resources/language/javascript/promises/simplifying-promises.md b/src/content/resources/language/javascript/promises/simplifying-promises.md
index d78f8af..0544d5a 100644
--- a/src/content/resources/language/javascript/promises/simplifying-promises.md
+++ b/src/content/resources/language/javascript/promises/simplifying-promises.md
@@ -8,7 +8,7 @@ title: Simplifying Promises
 The first naive attempt, using new Promise for something that already returns a promise.
 
 ```js
-function doAsync(number) {
+function doAsync() {
   return new Promise(function (resolve, reject) {
     doDatabase().then(function (dbResult) {
       otherDbFunction(dbResult).then(function (secondResult) {
@@ -23,7 +23,7 @@ Turns out you don't need new Promise if you're working with a function that
 already returns a promise, you can just return the original thing.
 
 ```js
-function doAsync(number) {
+function doAsync() {
   return doDatabase().then(function (dbResult) {
     otherDbFunction(dbResult).then(function (secondResult) {
       return secondResult + 10;
@@ -36,7 +36,7 @@ You also don't have to nest `.then` functions, the whole point of promises
 is that they allow you to chain them sequentially.
 
 ```js
-function doAsync(number) {
+function doAsync() {
   return doDatabase()
     .then(function (dbResult) {
       return otherDbFunction(dbResult);
@@ -51,7 +51,7 @@ you also don't have to create a new function just to pass in one
 variable, you can pass in the entire function itself to the then block
 
 ```js
-function doAsync(number) {
+function doAsync() {
   return doDatabase()
     .then(otherDbFunction)
     .then(function (secondResult) {
@@ -63,7 +63,7 @@ function doAsync(number) {
 And you don't need those returns if you just have ES6 arrow functions
 
 ```js
-const doAsync = (number) =>
+const doAsync = () =>
   doDatabase()
     .then(otherDbFunction)
     .then((secondResult) => secondResult + 10);