summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorDivay Prakash <divayprakash@users.noreply.github.com>2019-05-11 02:03:54 +0530
committerGitHub <noreply@github.com>2019-05-11 02:03:54 +0530
commit30bc3f244b8f6f96d1d4f10753c06110c2a063d8 (patch)
tree222b713b7f94b94744b061c1cc34f59fe6e33737
parentb13f63e92805a5e6e574781953a1dbf6b9943352 (diff)
parent22b6835d34cc098828662bffdfe95a5acaef5835 (diff)
[haxe/en] Fix grammatical errors, closes #3513 (#3530)
[haxe/en] Fix grammatical errors, closes #3513
-rw-r--r--haxe.html.markdown4
1 files changed, 2 insertions, 2 deletions
diff --git a/haxe.html.markdown b/haxe.html.markdown
index f7633dbf..a31728e1 100644
--- a/haxe.html.markdown
+++ b/haxe.html.markdown
@@ -334,7 +334,7 @@ class LearnHaxe3 {
Switch statements in Haxe are very powerful. In addition to working
on basic values like strings and ints, they can also work on the
generalized algebraic data types in enums (more on enums later).
- Here's some basic value examples for now:
+ Here are some basic value examples for now:
*/
var my_dog_name = "fido";
var favorite_thing = "";
@@ -594,7 +594,7 @@ class ComplexEnumTest {
public static function example() {
var e1:ComplexEnum = IntEnum(4); // specifying the enum parameter
// Now we can switch on the enum, as well as extract any parameters
- // it might of had.
+ // it might have had.
switch(e1) {
case IntEnum(x) : trace('$x was the parameter passed to e1');
default: trace("Shouldn't be printed");