Passing the wrong object to hasOwnProperty method.

Author: brunocoelho

doc/en/object/hasownproperty.md

@@ -5,26 +5,26 @@ on its [prototype chain](#object.prototype), it is necessary to use the
 `hasOwnProperty` method which all objects inherit from `Object.prototype`.
 
 > **Note:** It is **not** enough to check whether a property is `undefined`. The
-> property might very well exist, but its value just happens to be set to 
+> property might very well exist, but its value just happens to be set to
 > `undefined`.
 
-`hasOwnProperty` is the only thing in JavaScript which deals with properties and 
+`hasOwnProperty` is the only thing in JavaScript which deals with properties and
 does **not** traverse the prototype chain.
 
     // Poisoning Object.prototype
-    Object.prototype.bar = 1; 
+    Object.prototype.bar = 1;
     var foo = {goo: undefined};
-    
+
     foo.bar; // 1
     'bar' in foo; // true
 
     foo.hasOwnProperty('bar'); // false
     foo.hasOwnProperty('goo'); // true
 
-Only `hasOwnProperty` will give the correct and expected result; this is 
-essential when iterating over the properties of any object. There is **no** other 
-way to exclude properties that are not defined on the object itself, but 
-somewhere on its prototype chain.  
+Only `hasOwnProperty` will give the correct and expected result; this is
+essential when iterating over the properties of any object. There is **no** other
+way to exclude properties that are not defined on the object itself, but
+somewhere on its prototype chain.
 
 ### `hasOwnProperty` as a Property
 
@@ -45,7 +45,7 @@ necessary to use an *external* `hasOwnProperty` to get correct results.
     ({}).hasOwnProperty.call(foo, 'bar'); // true
 
     // It's also possible to use the hasOwnProperty property from the Object property for this purpose
-    Object.prototype.hasOwnProperty.call(obj, 'bar'); // true
+    Object.prototype.hasOwnProperty.call(foo, 'bar'); // true
 
 
 ### In Conclusion