Update README.org

I think there was a typo.

README.org

@@ -22,7 +22,7 @@ A general is a leader. -- onioncheese
 The joke from when I worked in Google was "deprecated means stable" -- romwell
 #+END_QUOTE
 
-General.el will eventually (maybe a decade from now) be superseded by a rewrite, or I will recommend a different package instead.  However this does not mean I will "deprecate" general, only that I will not add new features and will recommend the rewrite to any newcomers.  If you are already happy with general, stick with it.  It has been stable for years and had very new few bug reports or feature requests.  I will not remove the package from MELPA, just limit changes to bug fixes.  All existing feature requests for general.el will either be implemented in the rewrite or have open issues on its tracker.  If you need any new functionality, you should switch (or use both as you gradually transition, e.g. the rewrite for new keybindings or specific cases).
+General.el will eventually (maybe a decade from now) be superseded by a rewrite, or I will recommend a different package instead.  However this does not mean I will "deprecate" general, only that I will not add new features and will recommend the rewrite to any newcomers.  If you are already happy with general, stick with it.  It has been stable for years and had very few new bug reports or feature requests.  I will not remove the package from MELPA, just limit changes to bug fixes.  All existing feature requests for general.el will either be implemented in the rewrite or have open issues on its tracker.  If you need any new functionality, you should switch (or use both as you gradually transition, e.g. the rewrite for new keybindings or specific cases).
 
 ** Roadmap
 To rewrite general.el, I have split its functionality into separate packages that I will incrementally develop and add to MELPA roughly in this order: