Merge branch 'master' of https://github.com/ganelson/inform

inform7/Internal/Inter/BasicInformKit/Sections/Flex.i6t

@@ -208,7 +208,7 @@ and we might have been able to squeeze some of it into the existing free
 space. But it ensures that heap invariant (b) above is preserved, and
 besides, running out of memory tends to be something you don't do only once.
 
-(The code below is a refinement on the original, suggested by Jesse McGrew,
+(The code below is a refinement on the original, suggested by Tara McGrew,
 which handles non-multiple blocks better.)
 
 =

resources/Documentation/Examples/ForDemonstrationPurposes.txt

@@ -7,7 +7,7 @@ For: Z-Machine
 
 Suppose we want to have a character who can dynamically learn new actions by observing the player performing them. We could do this by adding the actions to a list of things the character can do, but using a relation to express the same idea allows for tidier, easier-to-read code.
 
-Thanks to Jesse McGrew for the initial design of this example.
+Thanks to Tara McGrew for the initial design of this example.
 
 	{*}"For Demonstration Purposes"
 

resources/Documentation/Examples/Transmutations.txt

@@ -55,4 +55,4 @@ Suppose we want to have a machine in our game that can transmute one item into a
 
 In this example we have only defined a single set of transmutable objects, but we could easily expand to include other groups.
 
-(Thanks to Jesse McGrew for proposing this example.)
+(Thanks to Tara McGrew for proposing this example.)

resources/Documentation/The Recipe Book.txt

@@ -40,7 +40,7 @@ Thanks also go to ^{@Nick Montfort} for several conversations during the develop
 
 ^{@Jeff Nyman} provided extensive feedback about using <i>Writing with Inform</i> in workshops of aspiring IF authors from both programming and conventional fiction writing backgrounds. His observations about the concerns of conventional writers first encountering IF were especially useful, and had a great influence on the  organization of the <i>Recipe Book</i>. While the results may not meet all the needs he identified, we hope to have taken a step in the right direction.
 
-A few examples were contributed by denizens of rec.arts.int-fiction: ^{@Jesse McGrew}, ^{@Jon Ingold}, ^{@Mike Tarbert}, ^{@Eric Rossing}, and ^{@Kate McKee} offered such elegant implementations of various tasks that we have folded their contributions (with permission) into the <i>Recipe Book</i>.
+A few examples were contributed by denizens of rec.arts.int-fiction: ^{@Tara McGrew}, ^{@Jon Ingold}, ^{@Mike Tarbert}, ^{@Eric Rossing}, and ^{@Kate McKee} offered such elegant implementations of various tasks that we have folded their contributions (with permission) into the <i>Recipe Book</i>.
 
 Finally, these pages owe much to the questions and suggestions of Inform users on rec.arts.int-fiction and ifMUD.
 

resources/Documentation/Writing with Inform.txt

@@ -17409,7 +17409,7 @@ When Inform needs to find an extension, it looks here first, then in the install
 
 Extensions are identified by author and by name, so that a given author can produce their own range of extensions, and need only ensure that these are named differently from each other. If John Smith and Mary Brown each want to write an extension called "Following People", there is no conflict.
 
-The name of an extension, and of an author, should be written in Sentence Capitalisation: that is, upper case for the first letter in each word. (Inform uses this to minimise problems on machines where filenames are read with case sensitivity.) It is permitted for author names to include upper-case letters within words, as with the "G" in "^{@Jesse McGrew}". In general it is best to avoid accented or unusual letters in titles and author names, but the standard ISO Latin-1 characters should be allowed - for instance,
+The name of an extension, and of an author, should be written in Sentence Capitalisation: that is, upper case for the first letter in each word. (Inform uses this to minimise problems on machines where filenames are read with case sensitivity.) It is permitted for author names to include upper-case letters within words, as with the "G" in "^{@Tara McGrew}". In general it is best to avoid accented or unusual letters in titles and author names, but the standard ISO Latin-1 characters should be allowed - for instance,
 
 	Étude Pour La Fênetre by Françoise Gauß begins here.