Conflicting documentation in understanding ReplicateState

[NiekZndt]

In the documentation of the Client Side Prediction on the topic of Understanding ReplicateState under "Using States In Code" the following code snippet is provided the prevent movement in the future.

[Replicate]
private void MovePlayer(ReplicateData data, ReplicateState state = ReplicateState.Invalid, Channel channel = Channel.Unreliable)
{   
    //If in the future then simply zero out velocities
    //and exit the method to prevent checking any input logic.
    //Using this approach will allow objects to still collide with
    //the rigidbody.
    if (state.IsFuture())
    {
        _myPredictionRigidbody.Velocity(Vector3.Zero);
        _myPredictionRigidbody.AngularVelocity(Vector3.Zero);
        return;
    }
    
    float horizontal = data.Horizontal;
    
    Vector3 movement = new(horizontal, 0f, 0f);
    
    _predictionRigidbody.AddVelocity(movement);
    _predictionRigidbody.Simulate();
}

However looking at the api documentation PredictionRigidbody, addVelocity is not a method of PredictionRigidbody. And in the description of the Velocity method it states "Simulate should still be called normally." which it doesn't in the example. So is AddVelocity replaced with AddForce or just setting the velocity? Should simulate be invoked after setting te velocity to zero in the future?

the doc: https://firstgeargames.com/FishNet/api/api/FishNet.Object.Prediction.PredictionRigidbody.html
PredictionRigidbody api: https://firstgeargames.com/FishNet/api/api/FishNet.Object.Prediction.PredictionRigidbody.html