Typo in docs (#4210)

Minor typo in docs

---

#### Does this PR need a docs update or release note?

- [X]  Yes, it's included
- [ ] 🕐 Yes, but in a later PR
- [ ]  No

#### Type of change

<!--- Please check the type of change your PR introduces: --->
- [ ] 🌻 Feature
- [ ] 🐛 Bugfix
- [ ] 🗺️ Documentation
- [ ] 🤖 Supportability/Tests
- [ ] 💻 CI/Deployment
- [ ] 🧹 Tech Debt/Cleanup

#### Issue(s)

<!-- Can reference multiple issues. Use one of the following "magic words" - "closes, fixes" to auto-close the Github issue. -->
* #<issue>

#### Test Plan

<!-- How will this be tested prior to merging.-->
- [ ] 💪 Manual
- [ ]  Unit test
- [ ] 💚 E2E
This commit is contained in:
Eno Thereska 2023-09-08 18:15:53 +01:00 committed by GitHub
parent be59928f98
commit 59c541a7db
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -32,7 +32,7 @@ data integrity then this is always the safest option.
`corso restore onedrive --destination /my-latest-restore --backup a422895c-c20c-4b06-883d-b866db9f86ef`
}</CodeBlock>
When a destination is manually specified, all restored will appear in that top-level
When a destination is manually specified, all restored items will appear in that top-level
folder. In the example above, Corso will restore everything into `my-latest-restore`.
If that folder doesn't already exist, Corso will automatically create it. If it does
exist, the restore will use the existing folder, allowing you to restore to the same