Remove more words (#12852)

* remove 'basically' from docs

* remove 'simply' from docs

* remove most uses of 'just' from docs
This commit is contained in:
Charles Kerr 2018-05-08 00:16:09 -05:00 committed by GitHub
parent 86d023b02f
commit 4d078fdb03
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
32 changed files with 51 additions and 52 deletions

View file

@ -15,7 +15,7 @@ the following Python modules:
## macOS SDK
If you're simply developing Electron and don't plan to redistribute your
If you're developing Electron and don't plan to redistribute your
custom Electron build, you may skip this section.
For certain features (e.g. pinch-zoom) to work properly, you must target the

View file

@ -143,7 +143,7 @@ Try reinstalling 32bit Node.js.
### Error: ENOENT, stat 'C:\Users\USERNAME\AppData\Roaming\npm'
Simply making that directory [should fix the problem](https://stackoverflow.com/a/25095327/102704):
Creating that directory [should fix the problem](https://stackoverflow.com/a/25095327/102704):
```powershell
$ mkdir ~\AppData\Roaming\npm

View file

@ -45,7 +45,7 @@ can switch the download address to it via
`export LIBCHROMIUMCONTENT_MIRROR=http://7xk3d2.dl1.z0.glb.clouddn.com/`
If you only want to build Electron quickly for testing or development, you
can download just the shared library versions by passing the `--dev` parameter:
can download the shared library versions by passing the `--dev` parameter:
```sh
$ ./script/bootstrap.py --dev
@ -69,7 +69,7 @@ uses `R` and `D` instead. This is because `gyp` randomly crashes if there is
only one `Release` or `Debug` build configuration defined, and Electron only has
to generate one target at a time as stated above.
This only affects developers, if you are just building Electron for rebranding
This only affects developers, if you are building Electron for rebranding
you are not affected.
## Tests
@ -95,7 +95,7 @@ $ npm run build && npm test
You can make the test suite run faster by isolating the specific test or block
you're currently working on using Mocha's
[exclusive tests](https://mochajs.org/#exclusive-tests) feature. Just append
[exclusive tests](https://mochajs.org/#exclusive-tests) feature. Append
`.only` to any `describe` or `it` function call:
```js

View file

@ -10,7 +10,7 @@ requests, which will save you and the reviewers' time.
You can install `clang-format` and `git-clang-format` via
`npm install -g clang-format`.
To automatically format a file according to Electron C++ code style, simply run
To automatically format a file according to Electron C++ code style, run
`clang-format -i path/to/electron/file.cc`. It should work on macOS/Linux/Windows.
The workflow to format your changed code:

View file

@ -160,7 +160,7 @@ $ npm run test
Make sure the linter does not report any issues and that all tests pass.
Please do not submit patches that fail either check.
If you are updating tests and just want to run a single spec to check it:
If you are updating tests and want to run a single spec to check it:
```sh
$ npm run test -match=menu

View file

@ -55,7 +55,7 @@ the content layer. For example to implement Pepper API, we need some wiring
similar to what official Chrome does. We could have built the relevant
sources as a part of [libcc](../glossary.md#libchromiumcontent) but most
often we don't require all the features (some tend to be proprietary,
analytics stuff) so we just took parts of the code. These could have easily
analytics stuff) so we took parts of the code. These could have easily
been patches in libcc, but at the time when these were written the goal of
libcc was to maintain very minimal patches and chromium_src changes tend to be
big ones. Also, note that these patches can never be upstreamed unlike other