Skip to content

Typography update #481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 28, 2018
Merged

Typography update #481

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
316594a
Typography update
EirikBirkeland Mar 28, 2018
c536571
Update command-line.md
EirikBirkeland Mar 28, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 7 additions & 8 deletions source/guides/guides/command-line.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ DEBUG=cypress:launcher cypress run --browser chrome

***Run tests in Electron in headed mode***

By default Cypress will run tests in Electron headlessly.
By default, Cypress will run tests in Electron headlessly.

Passing `--headed` will force Electron to be shown. This matches how you run Electron in the GUI.

Expand Down Expand Up @@ -123,9 +123,9 @@ cypress run --spec cypress/integration/app_spec.js

***Run tests specifying a project***

By default Cypress expects your `cypress.json` to be found where your `package.json` is. However, you can point Cypress to run on a different location.
By default, Cypress expects your `cypress.json` to be found where your `package.json` is. However, you can point Cypress to run in a different location.

This enables you to install Cypress in a top level `node_modules` folder but run Cypress on a nested folder. This is also helpful when you have multiple Cypress projects in your repo.
This enables you to install Cypress in a top level `node_modules` folder but run Cypress in a nested folder. This is also helpful when you have multiple Cypress projects in your repo.

To see this in action we've set up an {% url 'example repo to demonstrate this here' https://github.com/cypress-io/cypress-test-nested-projects %}.

Expand Down Expand Up @@ -209,7 +209,7 @@ cypress open --global

## `cypress verify`

Verify that Cypress is installed correctly and executable.
Verify that Cypress is installed correctly and is executable.

```shell
cypress verify
Expand All @@ -225,9 +225,8 @@ Cypress application is valid and should be okay to run: /Applications/Cypress.ap

Equivalent: `cypress --version`, `cypress -v`

Output both the versions of the the installed Cypress binary application and NPM module.
In most cases they will be the same, but could be different if you have installed a different
version of NPM package and for some reason could not install the matching binary.
Output both the versions of the installed Cypress binary application and NPM module.
In most cases they will be the same, but could be different if you have installed a different version of the NPM package and for some reason could not install the matching binary.

```shell
cypress version
Expand All @@ -248,7 +247,7 @@ You can use also require Cypress as a node module.
The Cypress module is brand new and we are still adding more functionality to it. Its API may change in the future.
{% endnote %}

Here's an example of programmatically running a spec spec file:
Here's an example of programmatically running a spec file:

```js
const cypress = require('cypress')
Expand Down