Yes, we’ve already caught that error in the documentation and it is fixed in our next release 17.02.
Thanks, Sarra
