Permalink
Browse files

Merge pull request #64 from breakerfall/1.5.2

Update book/index.html
  • Loading branch information...
2 parents 3b38914 + 36bf201 commit 5104bb88d71fbc6720dd40f84dfc306b71a08a53 @addyosmani committed Dec 26, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 book/index.html
View
@@ -2920,7 +2920,7 @@ <h2 id="prototypepatternjavascript">
<p>We can think of the prototype pattern as being based on prototypal inheritance where we create objects which act as prototypes for other objects. The prototype object itself is effectively used as a blueprint for each object the constructor creates. If the prototype of the constructor function used contains a property called <code>name</code> for example (as per the code sample lower down), then each object created by that same constructor will also have this same property.</p>
-<p>Reviewing the definitions for this pattern in existing (non-JavaScript literature), we <strong>may</strong> find references to classes once again. The reality is that prototypal inheritance avoids using classes altogether. There isn't a "definition" object nor a core object in theory. we're simply creating copies of existing functional objects.</p>
+<p>Reviewing the definitions for this pattern in existing (non-JavaScript) literature, we <strong>may</strong> find references to classes once again. The reality is that prototypal inheritance avoids using classes altogether. There isn't a "definition" object nor a core object in theory. we're simply creating copies of existing functional objects.</p>
<p>One of the benefits of using the prototype pattern is that we're working with the prototypal strengths JavaScript has to offer natively rather than attempting to imitate features of other languages. With other design patterns, this isn't always the case.</p>

0 comments on commit 5104bb8

Please sign in to comment.