From 6a8a9db4a14a3779f7c959640d286f8f5fb5419e Mon Sep 17 00:00:00 2001 From: James Stafford Date: Thu, 28 Jun 2018 18:04:12 -0700 Subject: [PATCH] fix(challenges): removed comment in the seed --- .../05-apis-and-microservices/managing-packages-with-npm.json | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/challenges/05-apis-and-microservices/managing-packages-with-npm.json b/challenges/05-apis-and-microservices/managing-packages-with-npm.json index cea543fc911..da7f8f4a67d 100644 --- a/challenges/05-apis-and-microservices/managing-packages-with-npm.json +++ b/challenges/05-apis-and-microservices/managing-packages-with-npm.json @@ -88,7 +88,6 @@ "id": "587d7fb4367417b2b2512bfe", "title": "Add a License to Your package.json", "description": [ - "TODO: This challenge could be used to inspire more people to develop OSS - we should really improve this description.", "The license-field is where you inform users of your project what they are allowed to do with it.", "Some common licenses for open source projects include MIT and BSD. http://choosealicense.com is a great resource if you want to learn more about what license could fit your project.", "License information is not required. Copyright laws in most countries will give you ownership of what you create by default. However, it’s always a good practice to explicitly state what users can and can’t do.", @@ -269,4 +268,4 @@ "translations": {} } ] -} \ No newline at end of file +}