diff --git a/doc/info/pl1lib.102 b/doc/info/epl1.103
similarity index 88%
rename from doc/info/pl1lib.102
rename to doc/info/epl1.103
index 21633896..b4699f01 100644
--- a/doc/info/pl1lib.102
+++ b/doc/info/epl1.103
@@ -1,12 +1,12 @@
 
-File: PL1LIB	Node: TOP	Next: USER	Up: (DIR)
+File: EPL1	Node: TOP	Next: USER	Up: (DIR)
 
-    The EMACS library PL1LIB contains macros to help edit PL1
-code.  Since PL1 indentation styles vary a lot, the PL1LIB macros are
+    The EMACS library PL1 contains macros to help edit PL1
+code.  Since PL1 indentation styles vary a lot, the PL1 macros are
 structured into an extensible scheme that allows the user control
 over the kinds of indenting done.
 
-    Load these macros into an EMACS, by MM Load Library$PL1LIB$$.
+    Load these macros into an EMACS, by MM Load Library$PL1$$.
 Then MM PL1 Mode$$ will set things up for editing PL1 code, such as
 setting comment delimiters, and putting the statement indenter into
 TAB.  If you want to set things up differently, you can provide a
@@ -35,7 +35,7 @@ Don't even do:
     Everyone should acquaint themselves with ^R Indent PL1 Statement
 (do "M User Calls" or just "N" to read about it). After that, you can
 read about various indentation subrs to handle common PL1 statements
-that are provided in the basic PL1LIB library (by doing "M Finished"
+that are provided in the basic PL1 library (by doing "M Finished"
 or "M Unfinished" from here, or just "N" from Indent Stmt). Those
 interested in writing their own indentation subrs can read through
 other parts of this info file.
@@ -43,7 +43,7 @@ other parts of this info file.
     To insert a full description of the PL1 commands, ^R macros, and
 subrs you can do:
 	MM Load Library$ABSTR$
-	MM Abstract File$ $ $PL1LIB$ 
+	MM Abstract File$ $ $PL1$ 
 Also, to keep up with changes or make suggestions, you can put
 yourself on the INFO-PL1-MODE mailing list on MC.
 
@@ -59,14 +59,14 @@ yourself on the INFO-PL1-MODE mailing list on MC.
 * Unfinished:	UNFIN	Indentation subrs called when previous stmt was
 			unfinished, i.e. really beginning of this one.
 
-* Subroutines:	SUBRS	PL1LIB provides several subroutines for moving
+* Subroutines:	SUBRS	PL1 provides several subroutines for moving
 			around PL1 code, for use by indentation subrs.
 
-File: PL1LIB	Node: USER	Next: USEFUL		Up: TOP
+File: EPL1	Node: USER	Next: USEFUL		Up: TOP
 
 ^R Indent PL1 Stmt:
 
-    The statement indenter is the main macro in the PL1LIB library. 
+    The statement indenter is the main macro in the PL1 library. 
 It indents a statement by an amount that depends on the previous
 statement's type, and whether it was finished (i.e. had a semi-colon
 at its end -- you can call ^R Indent PL1 Stmt to indent a part of a
@@ -116,7 +116,7 @@ suggest that you use this carefully, e.g. indenting small,
 screen-sized regions.  To protect against horrible mistakes, the old
 text is put on the kill stack, and point and MARK surround the new.
 
-File: PL1LIB	Node: USEFUL	Next: FIN	Previous: USER		Up: TOP
+File: EPL1	Node: USEFUL	Next: FIN	Previous: USER		Up: TOP
 
 Some related EMACS ^R macros that you may find useful, ordered by how
 useful I find them, are:
@@ -139,13 +139,13 @@ useful I find them, are:
 If you want more you can always MM Apropos$Indent$, or 
 MM Apropos$Comment$...
 
-File: PL1LIB	Node: FIN	Next: UNFIN	Previous: USEFUL	Up: Top
+File: EPL1	Node: FIN	Next: UNFIN	Previous: USEFUL	Up: Top
 
     This section documents the indentation subroutines called to
 handle new statements, i.e. there is nothing between here and the
 previous statement end (;) except labels and comments.  Such
 indentation subrs have names of the form & PL1 Indent After <TYPE>. 
-The PL1LIB library provides indentation subrs for finished previous
+The PL1 library provides indentation subrs for finished previous
 statements of type:
 	IF, ON, ELSE,		(the compound statement types)
 	DO, BEGIN,		(block beginners)
@@ -158,7 +158,7 @@ Stmt, just indents the same amount as the previous statement.  (If
 this is the first pl1 statement in the buffer, indentation is given
 by the variable $1st Stmt Indentation$, which has default 10.)
 
-* Menu:			More details on PL1LIB's indentation subrs.
+* Menu:			More details on PL1's indentation subrs.
 
 * Compound:	COMP	Compound statements, IF, ELSE and ON, look at 
 			the last sub-statement, e.g. IF ... THEN DO; vs
@@ -170,7 +170,7 @@ by the variable $1st Stmt Indentation$, which has default 10.)
 
 * End:		END	The END statement looks back for matching DO etc.
 
-File: PL1LIB	Node: COMP	Next: BLOCK	Up: FIN
+File: EPL1	Node: COMP	Next: BLOCK	Up: FIN
 
     The compound statements IF, ELSE, and ON contain sub-statements, and
 indenting after these depends on the last sub-statement: if this last
@@ -201,7 +201,7 @@ or
 	IF ... THEN BEGIN;
 			 here
 
-File: PL1LIB	Node: BLOCK	Next: PROC	Previous: COMP	Up: FIN
+File: EPL1	Node: BLOCK	Next: PROC	Previous: COMP	Up: FIN
 
     DO and BEGIN statements start blocks which are indented to align
 with the first non-whitespace following the DO or BEGIN, e.g.
@@ -215,12 +215,12 @@ or
 	DO  I = 1 TO 50;
 	    here
 
-File: PL1LIB	Node: PROC	Next: END	Previous: BLOCK	  Up: FIN
+File: EPL1	Node: PROC	Next: END	Previous: BLOCK	  Up: FIN
 
     Indent a constant amount, specified by $1st Proc Stmt Indentation$.
 If not exist, defaults to 10.
 
-File: PL1LIB	Node: END	Previous: PROC		Up: FIN
+File: EPL1	Node: END	Previous: PROC		Up: FIN
 
     END statements are the trickiest: they search back over
 preceeding statements until a matching DO, BEGIN, or PROC is found.
@@ -245,7 +245,7 @@ or
 		     END;
 	here
 
-File: PL1LIB	Node: UNFIN	Next: SUBRS	Previous: FIN	Up: TOP
+File: EPL1	Node: UNFIN	Next: SUBRS	Previous: FIN	Up: TOP
 
     The unfinished-IF indents the same amount as the IF, if the THEN
 hasn't occurred yet.  If it has, calls the default unfin-indenter.
@@ -263,7 +263,7 @@ Case 3: If prev line contains start of stmt, aligns with 1st word
         words, e.g. var_name is one token, two words).
 Case 4: Calls ^R PL1 Indent Relative if the above cases don't hold.
 
-File: PL1LIB	Node: SUBRS	Previous: UNFIN		Up: TOP
+File: EPL1	Node: SUBRS	Previous: UNFIN		Up: TOP
 
     There are several subroutines available for use by indentation
 subroutines, to help move to tokens past labels and comments, move to
@@ -277,7 +277,7 @@ finding ends of statements return a pointer to the semi-colon.
 
     For failed searches, generally either b or z is returned for values.
 
-    For more info on these subrs,  you can abstract PL1LIB as
+    For more info on these subrs,  you can abstract PL1 as
 mentioned earlier, or while it is loaded, you can MM List
 Subroutines$$ and MM Describe$$ whatever looks interesting.
 
