Sure, but that is an internal documentation failure not a redis failure. It feels incredibly unfair to blame redis for that.