I was going to recommend using headers to visually separate alternative strategies, but I suppose this removes the problem by the roots.

Also, in no particular order:

The menu bar wraps the last 2 boxes down onto a second line, I assume that's not intended.

Some of the text content exists only in an image. I generally recommend against this for accessibility reasons. it means the text can't be called up properly or accessed at all by a screen reader. (also there's no alt text to describe the image which could be another possible solution.) I understand why this would be a low priority for a video game walkthrough, but lots of people can benefit from these technologies, even if they are not totally blind.

I'm glad there's an index at the bottom of every page of the walkthrough. Maybe have it at the top of the body as well, for easy navigation if they were linked into the middle of the guide by someone?

Considering the importance and repetition of using the shield well, it may be a good idea to spend some time in the Templar instruction explaining the different features of the shield and how you would use them effectively in different situations.

It's probably a good idea to distinguish between alerting a gorgon so that they start to seek for you and being spotted by a Gorgon so that the gaze begins as two different events.

Thanks a lot, Pete. Appreciate you taking the time to go over it.

A follow-up question for you (and anyone else reading this):

I'm having a tough time with the final portion of the guide (everything after the jump puzzle). I'm torn as to how to approach it. On the one hand, it would be far simpler and easier to follow if I write a step-by-step guide, detailing a specific strategy, and that's it.
Faster to read, easier to understand.

What pulled me away from this is my experience playing with 1st time raiders. We'd give specific instructions: go here, shoot that, then run over here. But as soon as anything happened that wasn't part of the plan, they were lost. There was a lot of "I don't understand what just happened" because they didn't know why they were doing anything.

So my hope is that by explaining the mechanics behind the encounter, readers will understand what they're doing better. That way they'll be able to improvise and adjust when they need to.

BUT... I've clearly not done a good enough job explaining that section of the raid. Even I get confused when I read it lol.

All that being said, am I way off? Would it just be better to give basic step by step directions and skip the more general explanations?