[readme] Fix a typo

[IamAfnanSk]

Fixed: typo in README.md

[IamAfnanSk]

1 check still remains

[ljharb]

That’s fine; it’s Travis having trouble. Once i get that fixed, I’ll land this.

[IamAfnanSk]

Usually this don't take that much time? any idea what's happening?

[ljharb]

@IamAfnanSk it's a problem on travis' side. hopefully you don't mind leaving this open until i resolve it with them.

[IamAfnanSk]

Sure

[Abhra303]

In the README file, there is another mistake in the Troubleshooting on Linux . In the second line, the word "run" is repeated twice.
Alternatively, you can run *run* the following commands for the different shells on the command line:

[ljharb]

@IamAfnanSk unfortunately it seems like you deleted your fork, so i can't rebase and land this. Any chance you could restore it?

[IamAfnanSk]

@ljharb Hey! I don't have a copy locally and I also deleted from GitHub, so I think I won't be able to do so.

By any chance do you know about any other possibility?

[ljharb]

@IamAfnanSk my hope was that you could make a new fork on github, and git checkout 03859aa && git checkout -b patch-1 && git push, and that github would reconnect it to the PR. if that doesn't work tho, then there's probably no better option than me just pulling in the change directly :-(

[IamAfnanSk]

@ljharb I forked and tried git checkout 03859aa && git checkout -b patch-1 && git push but this doesn't seem to work.

fatal: reference is not a tree: 03859aa0de15d0835c9f85590bd25ea36f880fc2

[ljharb]

Interesting; you could probably add this repo as a remote and fetch from it to get the sha, but that’s getting complicated. I’ll try to land the change directly.

[ljharb]

Looks like this was fixed in 91bd22a / #2517.