spelling

Author: filipesilva

public/docs/ts/latest/cookbook/third-party-lib.jade

@@ -3,7 +3,7 @@ include ../_util-fns
 :marked
   Libraries are the backbone of the Angular ecosystem.
   They add functionality that would otherwise take a long time to implement from scratch and keep it up to date.
-  Everyone benifits from a healthy library ecosystem.
+  Everyone benefits from a healthy library ecosystem.
 
   Traditionally, third party JavaScript libraries have been published in the form of a single JavaScript file.
   Consumers of the library have then included the library, "as is", somewhere on the page using a `script` tag.
@@ -216,7 +216,7 @@ table(width="100%")
   Both [Ahead-of-time](#appendix-supporting-aot) and [Just-in-time](#appendix-supporting-it)
   compilation should be supported.
 
-  It's daunting to think of all the ways your library might be used and how to accomodate it, 
+  It's daunting to think of all the ways your library might be used and how to accommodate it, 
   but you don't need to have a "one-size-fits-all" library.
 
   You can configure `package.json` with more entry points besides [main](https://docs.npmjs.com/files/package.json#main).
@@ -405,7 +405,7 @@ code-example(language="json").
 :marked
   ## Appendix: Supporting JIT
 
-  AOT compiled code is the prefered format for production builds, but due to the long compilation time, it may not be practical to use AOT during development.
+  AOT compiled code is the preferred format for production builds, but due to the long compilation time, it may not be practical to use AOT during development.
 
   To create a more flexible developer experience, a JIT compatible build of the library should be published as well. The format of the JIT bundle is `umd`, which stands for Universal Module Definition. Shipping the bundle as `umd` ensures compatibility with most common module loading formats.