I'll bite: It's called Cognitive Load Management
Let's presume that your editor is not doing something stupid and is configure to use a fixed number of white spaces in tabs and you are not doing something stupid in your git commits.
You've written an algorithm that does X. A year later, when you are no longer on the project, I have to look into that code to fix a bug or add a new feature. Or... a year later, you are still around and have to do it. Before making any changes, that maintainer is going to have to read through the code to understand what it does and how it works. If you used significant - and consistent - whitespace indentation to enhance readability, the maintainer has to devote fewer "brain clock cycles" to understanding your coding style and has more to devote to understanding how it works and what needs to be done. This means that the change gets done faster and with less risk of regressions or other bugs.
- If you are using such a style anyway, then semicolons at the end of lines are moot.
- If you are using such a style anyway, then curly braces don't add much either. At best, they are irrelevant. At worst, they get used to space out the algorithm in such a way as to make it less readable and increase cognitive load.