docs: move await to explicit line for clarity

[iiio2]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Async function always returns a promise. There is no need to explicitly write await unless it is within try/catch. I think here await is kind of redundant.

https://eslint.org/docs/latest/rules/no-return-await
https://dev.to/danielbellmas/return-await-in-a-trycatch-4oh

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pi0]

Thanks for PR but probably await can stay there it was mostly to show users it returns a promise. (updated to make it two liner for more clarity)

[iiio2]

Thanks @pi0.