-
Notifications
You must be signed in to change notification settings - Fork 394
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
fix various small typos #2507
fix various small typos #2507
Conversation
@@ -78,7 +78,7 @@ dependencies (for example, a training datset tracked by DVC) have been found. So | |||
if you had a hypoethetical DVC pipeline whose final process was `deploy.dvc`, | |||
you could run `dvc repro -f deploy.dvc` to rerun the whole pipeline. | |||
|
|||
### Q: What's the best way to orgnize DVC repositories if I have several training datasets shared by several projects? Some projects use only one dataset while other use several. [Can one project have `.dvc` files corresponding to different remotes?](https://discordapp.com/channels/485586884165107732/563406153334128681/670664813973864449) | |||
### Q: What's the best way to oragnize DVC repositories if I have several training datasets shared by several projects? Some projects use only one dataset while other use several. [Can one project have `.dvc` files corresponding to different remotes?](https://discordapp.com/channels/485586884165107732/563406153334128681/670664813973864449) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job spotting all these typos! Is this one supposed to be organize
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops 🙈 I will claim
Muphry's law is an adage that states: "If you write anything criticizing editing or proofreading, there will be a fault of some kind in what you have written."[1] The name is a deliberate misspelling of "Murphy's law".
on this one!
Fixed in fe96ab5
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Many thanks @sixhobbits ! appreciate all the small fixes. There's just one I'm not too sure about but we can take care of rephrasing it. ✔️
p.s. This reminds me that it would be nice to have an automatic spell/grammar checker... Could try https://github.com/marketplace/actions/check-spelling or https://github.com/marketplace/actions/check-spelling-js-vue-html-markdown-text for now (cc @shcheklein @iesahin @casperdcl WDYT?) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will commit:
@@ -8,7 +8,7 @@ Git.' | |||
# Get Started: Data Versioning | |||
|
|||
How cool would it be to make Git handle arbitrary large files and directories |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How cool would it be to make Git handle arbitrary large files and directories | |
How cool would it be to make Git handle arbitrarily large files and directories |
@@ -8,7 +8,7 @@ Git.' | |||
# Get Started: Data Versioning | |||
|
|||
How cool would it be to make Git handle arbitrary large files and directories | |||
with the same performance as with small code files? Imagine doing a `git clone` | |||
with the same performance that you get with small code files? Imagine doing a `git clone` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
with the same performance that you get with small code files? Imagine doing a `git clone` | |
with the same performance it has with small code files? Imagine doing a `git clone` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh hm... I'm unable to commit #2507 (review). This PR doesn't allow maintainers to change its branch.
Fixed and merged #2508 instead 🙂 |
* ref: -c option typos * start: typo per #2507 (comment) * test: md link style (1) * guide: refactor md links in external data page * start: undo typo fix * ref: md ref link * api: use ref links
* ref: -c option typos * start: typo per #2507 (comment) * test: md link style (1) * guide: refactor md links in external data page * start: undo typo fix * ref: md ref link * api: use ref links * ref: clarify gdrive_service_account_user_email GDrive remote param
* ref: -c option typos * start: typo per #2507 (comment) * test: md link style (1) * guide: refactor md links in external data page * start: undo typo fix * ref: md ref link * api: use ref links * ref: clarify gdrive_service_account_user_email GDrive remote param * ref: fix help outputs
* ref: -c option typos * start: typo per #2507 (comment) * test: md link style (1) * guide: refactor md links in external data page * start: undo typo fix * ref: md ref link * api: use ref links * ref: clarify gdrive_service_account_user_email GDrive remote param * ref: fix help outputs * docs: bash -> dvc per #2654 (comment)
* ref: -c option typos * start: typo per #2507 (comment) * test: md link style (1) * guide: refactor md links in external data page * start: undo typo fix * ref: md ref link * api: use ref links * ref: clarify gdrive_service_account_user_email GDrive remote param * ref: fix help outputs * ref: update Vega links
This fixes various small typos across the blog and docs.
We, Ritza, are a team of technical writers, editors, engineers, and quality assurance specialists. We create new technical content, such as developer tutorials, for highly technical products, and help improve and maintain existing developer documentation sites.