Index: maintain.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/maintain.texi,v
retrieving revision 1.283
diff -u -r1.283 maintain.texi
--- maintain.texi	27 Feb 2022 04:00:30 -0000	1.283
+++ maintain.texi	9 Jun 2023 03:20:07 -0000
@@ -5,7 +5,7 @@
 @c For double-sided printing, uncomment:
 @c @setchapternewpage odd
 @c This date is automagically updated when you save this file:
-@set lastupdate February 26, 2022
+@set lastupdate June 8, 2023
 @c %**end of header
 @documentencoding UTF-8
 
@@ -2267,7 +2267,7 @@
 @file{foo-1.0.tar.gz} and @file{foo-1.0.tar.gz.sig} will be placed in the
 directory @file{gnu/bar/v1} of the @code{ftp.gnu.org} site.
 
-The directive file can be used to create currently non-existent
+The directive file can be used to create currently nonexistent
 directory trees, as long as they are under the package directory for
 your package (in the example above, that is @code{bar}).
 
@@ -2446,10 +2446,10 @@
 images is still not recommended, as the PNG and JPEG formats are
 generally superior.  See @url{https://www.gnu.org/philosophy/gif.html}.
 
-Please make sure that any Javascript code in your web pages is covered
+Please make sure that any JavaScript code in your web pages is covered
 by a free license, and has its license indicated in a way LibreJS can
 recognize.  See @url{https://gnu.org/philosophy/javascript-trap.html}.
-If the Javascript in the page is minified, or for any other reason is
+If the JavaScript in the page is minified, or for any other reason is
 not the source code, it must point to its source code as described
 there.
 
Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.272
diff -u -r1.272 standards.texi
--- standards.texi	17 Aug 2021 13:21:06 -0000	1.272
+++ standards.texi	9 Jun 2023 03:20:07 -0000
@@ -4607,19 +4607,19 @@
 
 A web page recommends a program in an implicit but particularly strong
 way if it requires users to run that program in order to use the page.
-Many pages contain Javascript code which they recommend in this way.
-This Javascript code may be free or non-free, but non-free is the usual
+Many pages contain JavaScript code which they recommend in this way.
+This JavaScript code may be free or non-free, but non-free is the usual
 case.
 
 If the purpose for which you would refer to the page cannot be carried
-out without running non-free Javascript code, then you should not refer
+out without running non-free JavaScript code, then you should not refer
 to it.  Thus, if the purpose of referring to the page is for people to
 view a video, or subscribing to a mailing list, and the viewing or
 subscribing fail to work if the user's browser blocks the non-free
-Javascript code, then don't refer to that page.
+JavaScript code, then don't refer to that page.
 
 The extreme case is that of web sites which depend on non-free
-Javascript code even to @emph{see} the contents of the pages.  Any
+JavaScript code even to @emph{see} the contents of the pages.  Any
 site hosted on @indicateurl{wix.com} has this problem, and so do some
 other sites.  Referring people to such pages to read their contents
 is, in effect, urging them to run those non-free programs---so please