-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Feedback for: machine/get-started.md #134
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.
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
Comments
@engcheng I can't repro there being more than one link. Which browser are you using? |
@johndmulhausen thanks for feedback. I'm using Firefox 45.4.0 on Linux 64 bits. The url with typo which I'm referring to can be traced in the following sequence:
I've also attached a screenshot for further clarity in PicPaste Hope its clearer now. |
Thanks, @engcheng that does help, especially the screenshot. :) So by "point to the same thing" you don't mean that there are two Hyper-V links pointing to the same thing, you mean that "Hyper-V" is being used twice in this sentence and it is not clear why, correct? |
yes @johndmulhausen If we break the statement into 2 parts, Substituting the product name by symbols, "Docker for Windows uses A for virtualization, and A and B are incompatible". Thus it creates an impression A is both compatible and incompatible. Think I get it. The first statement is stating what works. The second statement is saying what don't work, right? If that's the case, perhaps may I suggest:
Do you think its clearer? Thanks for taking time to enlighten 😄 |
I think I might understand this. You can't use Hyper-V with VirtualBox because they are incompatible. There are not enough specific nouns used in the sentence. Let me take a stab at this. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. /lifecycle locked |
URL: https://docs.docker.com/machine/get-started.md
Under the section, "If you are using Docker for Windows"
The first line mentions:
Is there a typo error? Because Hyper-V for virtualization and Hyper-V seems to be pointing to the same thing.
.
The text was updated successfully, but these errors were encountered: