From c9ddf0e15dbf8bf8a2b8137d0a8e8a020efc2cb9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Du=C5=A1an=20Jureti=C4=87?= Date: Sat, 11 Jan 2014 17:54:50 -0300 Subject: [PATCH] Fix typos --- script/content.coffee | 2 +- tests/algos.mocha.coffee | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/script/content.coffee b/script/content.coffee index 26f54f5a11..444d277fd1 100644 --- a/script/content.coffee +++ b/script/content.coffee @@ -231,7 +231,7 @@ api.potion = type: 'potion', text: "Health Potion", notes: "Recover 15 Health (I thing and receives another, it will cause errors. `self` is used for self buffs, multi-task debuffs, AOEs (eg, meteor-shower), etc. Basically, use self for anything that's not [task, party, user] and is an instant-cast - * {cast}: the fucntion that's run to perform the ability's action. This is pretty slick - because this is exported to the + * {cast}: the function that's run to perform the ability's action. This is pretty slick - because this is exported to the web, this function can be performed on the client and on the server. `user` param is self (needed for determining your own stats for effectiveness of cast), and `target` param is one of [task, party, user]. In the case of `self` spells, you act on `user` instead of `target`. You can trust these are the correct objects, as long as the `target` attr of the diff --git a/tests/algos.mocha.coffee b/tests/algos.mocha.coffee index 1af5a32225..096f597bee 100644 --- a/tests/algos.mocha.coffee +++ b/tests/algos.mocha.coffee @@ -205,7 +205,7 @@ describe 'User', -> describe 'spells', -> _.each shared.content.spells, (spellClass)-> _.each spellClass, (spell)-> - it "#{spell.text} have a valid target", -> + it "#{spell.text} has a valid target", -> expect(spell.target).to.match(/^(task|self|party|user)$/) describe 'drop system', ->