summaryrefslogtreecommitdiffhomepage
path: root/javascript.html.markdown
diff options
context:
space:
mode:
authorjasonqu <qiuguo0205@gmail.com>2015-03-06 17:42:44 +0800
committerjasonqu <qiuguo0205@gmail.com>2015-03-06 17:42:44 +0800
commit5e0964e2eee068b872fb0d61b5398997e0b76670 (patch)
tree20ece4ef5e868e770f1487804af2bed180041095 /javascript.html.markdown
parent303ec58a52cef60d8fdc13babe378f4a2e6117c3 (diff)
[javascript/zh] Translation tracking
Diffstat (limited to 'javascript.html.markdown')
-rw-r--r--javascript.html.markdown4
1 files changed, 2 insertions, 2 deletions
diff --git a/javascript.html.markdown b/javascript.html.markdown
index 95808d05..588ea86d 100644
--- a/javascript.html.markdown
+++ b/javascript.html.markdown
@@ -407,7 +407,7 @@ myNewObj.myNumber; // = 5
// look at its prototype.
// Some JS implementations let you access an object's prototype on the magic
-// property __proto__. While this is useful for explaining prototypes it's not
+// property `__proto__`. While this is useful for explaining prototypes it's not
// part of the standard; we'll get to standard ways of using prototypes later.
var myObj = {
myString: "Hello world!"
@@ -438,7 +438,7 @@ myObj.myBoolean; // = true
myPrototype.meaningOfLife = 43;
myObj.meaningOfLife; // = 43
-// We mentioned that __proto__ was non-standard, and there's no standard way to
+// We mentioned that `__proto__` was non-standard, and there's no standard way to
// change the prototype of an existing object. However, there are two ways to
// create a new object with a given prototype.