Personally i created bullet points describing the general activity the program should perform in order to reach the final task, the return of the variable of interest.
Then, for each bullet point i went down in the details, describing the functions that the program performs for that activity, as code but in words.
Kinda this link: https://www.unf.edu/~broggio/cop2221/2221pseu.htm
that Quellocinese posted.
That is the best alternative also for readibility of the pseudo-code.
i had a look at the 3 peer assessments, all of them written word file alike.
How am i supposed to understand those codes is a mistery. Also how am i supposed to evaluate the correctness and the efficiency of that code if is written like "i created a list comprehension because is fast"...yeah so, what variables did you use? how did you created it? what was your objective? and did it work?
in my pseudo-code i tried to answer those questions also to make a favour to who will read it, you know? to spend the least amount of time and resources as possible. i think that the guy who received mine will appreciate it. Dunno.