One issue I found is when I press the apply button it gets a socket failed error

Works as expected! One issue I found is when I press the apply button it gets a socket failed error

Looking at the stack trace, it seems to be a Unity Transport bug. the Latency and Jitter are correctly applied even with that error showing up. I don't think we can do much about it apart from reporting it to the Transport team.

It only happens when I try to apply something from the host, maybe that is expected somehow? when using apply with a client it works

Yes, I'll ask 👀
EDIT: done here

It also failed now once or twice when working with client.

But also it talks about changing the top slider will update the bottom slider. I do not see any slider following another one here. How does it work, wasn't the layout different before?

it talks about changing the top slider will update the bottom slider. I do not see any slider following another one here. How does it work, wasn't the layout different before?

Nice catch, the layout was different before. I changed it after updating the label, and forgot to update the text. Will do it now!

The explanation looks good! Just one thing I am wondering is to maybe explain the shadow to users when moving with WASD, e.g. does it display what the server is anticipating or how the client is moving?

maybe explain the shadow to users when moving with WASD,

That's what we'll do in the tutorial ( https://jira.unity3d.com/browse/MTT-8702 )

e.g. does it display what the server is anticipating or how the client is moving?

The ghost displays where the player is on the server, while the non-ghost is the anticipated position of the player (= where the Client thinks the server player will end up being). The ghost following the player's trail is the "Reconciliation" part of the process.

A tutorial perfect that settles things then! And thanks for the explanation, so ghost is server and non-ghost is the anticipation of the client.