A reminder for folks just starting out (or anyone with anxiety around code reviews):
Think of it as the editing step in novel writing. No one believes an author, no matter how distinguished, can edit their own material and the same stands for software.
You will miss little details. You'll have quirks that you can't see till they're pointed out. This is all normal. It's not a failure to have to make changes after review.
Beyond that, as I've noted before, PRs are a key mechanism for team communication. They're an important way that we stay up to date on how all of the code base functions, even the bits we aren't actively working on.