Graham/angular-cli
1
0
Fork 0
mirror of https://github.com/angular/angular-cli.git synced 2025-05-21 22:34:21 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typos in multiple files

Browse Source
This commit is contained in:
Schneider 2020-02-02 13:15:50 -02:00 committed by Douglas Parker
parent 4e65705205
commit 2c10cf80f6
4 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/process/release.md
View File

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

2
packages/angular/cli/README.md
View File

@ -237,7 +237,7 @@ To capture a CPU profiling, you can:
* on Windows: ̀̀`setx NG_CLI_PROFILING my-profile` * on Windows: ̀̀`setx NG_CLI_PROFILING my-profile`
Then, just run the ng command on which you want to capture a CPU 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: You can use the Chrome Devtools to process it. To do so:
1. open `chrome://inspect/#devices` in Chrome 1. open `chrome://inspect/#devices` in Chrome

2
packages/angular_devkit/core/src/experimental/jobs/architecture.md
View File

@ -90,7 +90,7 @@ This seems like a lot of boilerplate in comparison, but there are a few advantag
## Diagram ## Diagram
A simpler way to think about jobs in contrast to observables is that job are closer to a Unix 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 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). (piping), and can be transformed, synchronized and scheduled (fork, exec, cron).