If all a page says is "See WikiPage", load WikiPage instead of the originally requested page. That way, synonyms, alternative spellings and singular-vs-plural issues are easily dealt with.

''But the original page becomes impossible to edit in the case that the redirect was wrong or needs updating.''

[This is not a problem.  Either someone can edit the url and insert edit=PageName, or the script could just do a sleep(0.5), keeping an edit link that a user can stop and then click.]

{What script is that? If it's WardsWiki, it will not be updated for the foreseeable future.}

Well, there should be ways to provide for that.
	For example::	The page Category''''''Homepage ('wrong' capitalization) says "See CategoryHomePage". If readers follow the link to Category''''''Homepage, they get redirected to CategoryHomePage. That page displays a header saying "Redirected from Category''''''Homepage". Readers following that link would get to the actual Category''''''Homepage, which would then be editable in the usual way.

Also, we should check for circular redirecting; the easiest way to avoid that would probably be to not redirect as result of a redirect. In the example above, that would mean that if the page CategoryHomePage would say "See HomePage" in turn, you wouldn't get redirected again, but just see those two words. Another solution would be redirecting away, stacking all redirection headers as we go along, detecting circles (it's not RocketScience) and displaying the page that would 'close the circle', including all the headers. That way, a reader could try to resolve it by editing any of the redirecting pages. -- AalbertTorsius

[Circular redirects shouldn't be a problem, either the load will stay low until the user clicks the stop button, or the system might notice and flag the unusual activity -- when it even happens at all.]

{Resolving circular references would be technically trivial, but as this Wiki is considered a legacy application, implementation of WikiRedirect as described above will not happen.}