Skip to content

Commit 6439ee9

Browse files
Add style and phrasing nitpicks
Signed-off-by: Nathan LeClaire <nathan.leclaire@gmail.com>
1 parent 5358010 commit 6439ee9

File tree

1 file changed

+16
-14
lines changed

1 file changed

+16
-14
lines changed

docs/get-started.md

Lines changed: 16 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -143,17 +143,19 @@ Make sure to specify the machine name as an argument:
143143
# Crash Reporting
144144

145145
Provisioning a host is a complex matter that can fail for a lot of reasons.
146-
Some of those reasons lies in your very workstation that can have a wide
147-
variety of shell, network configuration, vpn, proxy and firewalls or from reasons
148-
on the other end of the chain: your cloud provider or the network in between.
149-
150-
To help `docker-machine` be as stable as possible, we added a monitoring of crashes
151-
whenever you try to `create` or `upgrade` a host. This will send over https to bugsnag
152-
a couple of information : your docker-machine version, build, OS, ARCH, the path to your
153-
current shell and the history of the last command as you could see it with a `-D` option.
154-
Those data are only there to help us pinpoint recurring issue with docker-machine and will only
155-
be transmitted in the case of a crash of docker-machine.
156-
157-
If you're worried about thatm you can create a `no-error-report` in the `$HOME/.docker/machine`
158-
directory, and we will not gather nor send any data.
159-
146+
Your workstation may have a wide variety of shell, network configuration, VPN,
147+
proxy or firewall issues. There are also reasons from the other end of the
148+
chain: your cloud provider or the network in between.
149+
150+
To help `docker-machine` be as stable as possible, we added a monitoring of
151+
crashes whenever you try to `create` or `upgrade` a host. This will send, over
152+
HTTPS, to Bugsnag some information about your `docker-machine` version, build,
153+
OS, ARCH, the path to your current shell and, the history of the last command as
154+
you could see it with a `--debug` option. This data is sent to help us pinpoint
155+
recurring issues with `docker-machine` and will only be transmitted in the case
156+
of a crash of `docker-machine`.
157+
158+
If you wish to opt out of error reporting, you can create a `no-error-report`
159+
file in your `$HOME/.docker/machine` directory, and Docker Machine will disable
160+
this behavior. Leaving the file empty is fine -- Docker Machine just checks for
161+
its presence.

0 commit comments

Comments
 (0)