Paxos is correct and Raft is correct. The difference is that Raft was designed to be understood, and that design decision shows up everywhere: in the vocabulary, in the shape of the state machine, and in what you have to hold in your head at once.
Raft splits the problem into three pieces that can be explained on their own: leader election, log replication, and safety. You can learn each one with the others switched off. Paxos gives you a single protocol that does all three at once, which is elegant on paper and hard on a whiteboard.
The second trick is the strong leader. In Raft, log entries only ever flow from the leader to followers, so most of the corner cases simply cannot happen. That constraint costs a little availability during elections and buys a lot of clarity the rest of the time.
None of this makes Raft better. It makes Raft teachable, and a protocol people can hold in their head is a protocol people implement correctly.