# Documentation typos

**URL:** https://forums.creativeclouddeveloper.com/t/documentation-typos/3785
**Category:** UXP Plugin API
**Created:** [October 23, 2021, 5:13pm UTC](https://forums.creativeclouddeveloper.com/t/documentation-typos/3785 "2021-10-23T17:13:57Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![cwallstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/cwallstrom/32/1701_2.png) [@cwallstrom](https://forums.creativeclouddeveloper.com/u/cwallstrom)
#### Post date: [October 23, 2021, 5:13pm UTC](https://forums.creativeclouddeveloper.com/t/documentation-typos/3785/1 "2021-10-23T17:13:57Z")

</div>

Not a big deal, but may confuse new users. In a lot of places you have the equal sign ‘=’ when passing in object properties in your examples. Such as this  
const folder = await fs.getFolder({initialDomain = domains.userDocuments});

When it should use ‘:’  
const folder = await fs.getFolder({initialDomain: domains.userDocuments});

---

<div class="post-metadata">

### Author: ![pklaschka](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/pklaschka/32/3162_2.png) [@pklaschka](https://forums.creativeclouddeveloper.com/u/pklaschka)
#### Post date: [October 23, 2021, 10:07pm UTC](https://forums.creativeclouddeveloper.com/t/documentation-typos/3785/2 "2021-10-23T22:07:04Z")

</div>

Hi @cwallstrom ,

Thanks for reporting this.

It’s already (somewhat) getting tracked in [Wrong parameters and examples in `FileSystemProvider.getFileForSaving()` · Issue #53 · AdobeDocs/uxp · GitHub](https://github.com/AdobeDocs/uxp/issues/53) and [createPersistentToken() is actually asynchronous · Issue #54 · AdobeDocs/uxp · GitHub](https://github.com/AdobeDocs/uxp/issues/54) (at least it’ll get fixed in the same batch that also fixes this issue; you can see them as “there are various issues with the file storage docs”). I’m already on it, unfortunately, updating this part of the docs is a bit of a process (it first has to get fixed on an internal code base from which new documentation gets generated 😅 ), but we’re on it 🙂 .
