X-Git-Url: https://code.delx.au/gnu-emacs-elpa/blobdiff_plain/1254161ead31da9dab50af0ae682c12a1244b338..af1503e299857e5c3d3a04c50a32e00c968ed494:/README

diff --git a/README b/README
index f3fd32b34..fe5a4f1ac 100644
--- a/README
+++ b/README
@@ -2,7 +2,7 @@ Copyright (C) 2010-2011, 2014 Free Software Foundation, Inc.
 See the end of the file for license conditions.
 
 
-This branch contains the sources, deployment scripts, and auxilliary
+This branch contains the sources, deployment scripts, and auxiliary
 files for the Emacs Lisp package archive (elpa.gnu.org).
 
 This file explains the branch layout, how to add and edit packages,
@@ -39,9 +39,9 @@ release the new code.
 *** Add a simple (1-file) package as packages/<pkg-name>/<pkg-name>.el.
 
 The file needs to follow the usual coding conventions (most
-importantly start with ";;; <file> --- <description>") as well as the
-package headers required by package.el (see the "Format" subsection
-below).
+importantly start with ";;; <file> --- <description>") and have a
+"Version:" and "Maintainer:" pseudo-header (see the "Format"
+subsection below).
 
 For some examples, see
     (info "(elisp) Simple Packages")
@@ -134,7 +134,7 @@ simply commit further changes to it here.  Of course, this may trigger
 merge conflicts when you do a "subtree pull" in the future, so it's
 best to avoid these local changes.
 
-If someone makes changes to your package on here elpa.git and you want
+If someone makes changes to your package here on elpa.git and you want
 to push them to your remote, it's easiest to just copy these changes
 over to the remote repo.  Trying to push a subtree with git is likely
 to induce headache.