docs: fix typos in multiple files

docs/documentation/stories/create-library.md

@@ -74,7 +74,7 @@ You can read more about publishing on npm here:
 https://docs.npmjs.com/getting-started/publishing-npm-packages
 
 
-## Why do I need to build the library everytime I make changes?
+## Why do I need to build the library every time I make changes?
 
 Running `ng build my-lib` every time you change a file is bothersome and takes time.
 In `Angular CLI` version `6.2` an incremental builds functionality has been added to improve the experience of library developers. 

docs/process/release.md

@@ -119,7 +119,7 @@ Run `npm login`:
     * The app will start showing two-factor codes, enter one into the
         `npm login` prompt.
 
-Once sucessfully logged in, it is time to publish.
+Once successfully logged in, it is time to publish.
 
 ### Publishing
 

packages/angular/cli/README.md

@@ -237,7 +237,7 @@ To capture a CPU profiling, you can:
     * on Windows: ̀̀`setx NG_CLI_PROFILING my-profile`
 
 Then, just run the ng command on which you want to capture a CPU profile.
-You will then obtain a `my-profile.cpuprofile` file in the folder from wich you ran the ng command.
+You will then obtain a `my-profile.cpuprofile` file in the folder from which you ran the ng command.
 
 You can use the Chrome Devtools to process it. To do so:
 1. open `chrome://inspect/#devices` in Chrome

packages/angular_devkit/core/src/experimental/jobs/architecture.md

@@ -90,7 +90,7 @@ This seems like a lot of boilerplate in comparison, but there are a few advantag
 
 ## Diagram
 A simpler way to think about jobs in contrast to observables is that job are closer to a Unix
-process. It has an argument (command line flags), receive inputs (STDIN and interupt signals),
+process. It has an argument (command line flags), receive inputs (STDIN and interrupt signals),
 and output values (STDOUT) as well as diagnostic (STDERR). They can be plugged one into another
 (piping), and can be transformed, synchronized and scheduled (fork, exec, cron).