@User we have updated the docs to fix this error. Thanks for pointing it out 🙂