What he's saying is curly brackets are opened in pairs ie { ... } and they must balance as we all know. So the closing bracket should be labelled with a comment to show which opening bracket it refers to:
1 2 3 4 5 6 7 8 9 10
{ // this opens bracket pair 1
{ // this opens bracket pair 2
} // this closes bracket pair 2
} // this closes bracket pair 1
You won't see a lot of code here doing that but it's not wrong to do it. Just play the game - after all, he's dishing out the marks, Ray's the man.
PS same goes for general comments. Good programming is pretty much self documenting. A good header statement using various conventions avoids clutter with redundant commentary but again just play the game. :)
PPS As a hint use your pseudocode as the comments combined with the header statement. ( That's if you've written some. )
The Value of a Source Code is calculated by "code metrics". A code has to be readable and understandable for other users therefore comments in your source code is better than not comments or few comments.