Like King of Dragon Pass before it, Six Ages will have a lot of text. Which means a lot of opportunity for typos or other misspellings.
Most of the text is in OSL scripts, such as these excerpts:
saga: <expeditionLeader> was attacked, but returned home with <his/her> escort. sagaText: The worshipers suffered the same fate. text: We eventually pieced this together from stories told by wandering traders.
The scene compiler outputs all strings into a single text file. It looks something like this:
<expeditionLeader> was attacked, but returned home with <his/her> escort. <expeditionLeader> was attacked and wounded, but returned home with <his/her> escort. Unfortunately, <he/she> lost the livestock they were driving home. <expeditionLeader> and <his/her> escort <disappeared mysteriously/were ambushed by trolls and completely devoured>. The worshipers suffered the same fate. We eventually pieced this together from stories told by wandering traders.
And that file can be spellchecked. I just use TextEdit. The biggest issue with proofreading is that the game uses a lot of proper names and jargon specific to Glorantha. Luckily it’s easy enough to add “Orlanth” to the dictionary (or the ignore list). More problematic is that variable names (like expeditionLeader) also show up here, though ignoring them usually works too.
Another issue is that it’s a big file. It may be generated by our tool but it still takes a human a while to review, so that doesn’t happen often (in fact the first complete review was today).
This is just a brute force pass. Many typos end up with words that are spelled correctly. And once in a while game-specific names get misspelled. So QA still needs to keep an eye open for problems.