Overhaul README.md.

Author: joaotavora

README.md

@@ -10,10 +10,12 @@ your way:
 * 📽 Scroll down this README for some [pretty gifs](#animated_gifs)
 * 📚 Read Eglot's [manual][manual] and [release notes][release-notes]
 * 🏆 Folks over at Google [seem to like it][gospb].  Thanks!
-* 👾 Eglot now lives in [Emacs itself](#emacscore)!
+* ✨ Get the [stable](#stable) or the [latest](#latest) version
+* 👾 Eglot now [lives in Emacs itself](#core)! Learn how to [contribute](#emacscore)!
 
-See also [eglot-x][eglot-x] for non-standard protocol extensions support.
+Also see [eglot-x][eglot-x] for non-standard protocol extensions support.
 
+<a name=stable></a>
 # Get stable [GNU ELPA][gnuelpa] version
 
 Just type `M-x package-install RET eglot RET` into Emacs 26.3+.
@@ -24,58 +26,20 @@ Now find some source file, any source file, and type `M-x eglot`.
 for the language you're using.  Otherwise, it prompts you to enter
 one.
 
-# Get latest development version from [GNU-Devel ELPA][gnudevelelpa]
+<a name=latest></a>
+# Get latest [GNU-Devel ELPA][gnudevelelpa] version
 
-First, configure this repository.
+First, configure GNU-Devel ELPA as your ELPA source repository.
 ```lisp
 (add-to-list 'package-archives '("gnu-devel" . "https://elpa.gnu.org/devel/"))
 ```
 
-Then, use `M-x package-install` or `M-x package-update` to install
-an ELPA package from the latest upstream.
+Then, use `M-x package-install` or `M-x package-update` as before install
+an ELPA package from the latest upstream.  You will be running the same 
+Eglot version as if you were running Emacs master! 
 
-<a name=emacscore></a>
-# Contribute to Eglot's development
-
-_**Eglot is now in Emacs's core!**_ Upcoming Emacs 29 will have `M-x
-eglot` built-in.
-
-The recommended way to experiment with changes to the latest Eglot is
-to [compile][compile-emacs1] [Emacs][compile-emacs2]
-[yourself][compile-emacs3-official].  
-
-From a development perspective, moving to core allows us to work on
-Eglot in tandem with other related packages already in Emacs, such as
-[Flymake][flymake], [ElDoc][eldoc], [Xref][xref], [Project][project].
-
-This means adding or tweaking an Emacs LSP feature is a matter of
-submitting a single patch targetting multiple relevant packages, not
-just Eglot.
-
-These `:core` packages (Eglot included) are then released periodically
-to GNU ELPA, so users of other Emacs's versions can get them via
-`M-x package-install`.
-
-# Status of this GitHub repository
-
-This repository is **not the development upstream anymore**, but it's
-**not** dead (yet):
-
-* It may be used to start [discussions][discussion].
-
-  Sometimes, it's possible the discussion or bug report will be moved
-  to [Emacs's bug tracker][emacs-bug-tracker-eglot].  You may take the
-  initiative and start discussion there using `M-x report-emacs-bug`
-  or simply sending mail to `bug-gnu-emacs@gnu.org`.
-  
-  Please the [Eglot-specific bug-reporting instructions][bug-reporting].
-  
-* The [`eglot.el`][eglot.el] file here is periodically updated to mirror
-  the [Emacs upstream][upstream-eglot.el]
-
-* The existing tests of [`eglot-tests.el`][eglot-tests.el], also
-  periodically updated, may be used to rehearse and validate patches
-  using [GitHub CI infrastructure][build-status].
+`M-x eglot-upgrade-eglot` should  also work if you have already installed 
+it. 
 
 <a name="connecting"></a>
 # Connecting to a server
@@ -125,6 +89,72 @@ variable, where you can [easily add your own servers][manual].
 * YAML's [yaml-language-server][yaml-language-server]
 * Zig's [zls][zls]
 
+
+<a name="core"></a>
+# Eglot is in Emacs's core since Emacs 29!
+
+⚠️ This repository is **not the development upstream anymore** ⚠️
+
+It's **not** dead (yet 🧟)
+
+* Pull requests **won't** be merged.  You can still use them to show ideas
+  for patches.  See [below](#emacscore) for how to properly contribute.
+
+* You can start a [discussion][discussion]
+
+  Say what is on your mind.  It's possible discussion or bug report will
+  be moved to [Emacs's bug tracker][emacs-bug-tracker-eglot].  You may
+  jump straight to that forum using `M-x report-emacs-bug` or simply
+  sending mail to `bug-gnu-emacs@gnu.org`.
+  
+  Please the [Eglot-specific bug-reporting instructions][bug-reporting].
+  
+* The [`eglot.el`][eglot.el] file here is periodically updated to mirror
+  the [Emacs upstream][upstream-eglot.el]
+
+* The existing tests of [`eglot-tests.el`][eglot-tests.el], also
+  periodically updated, may be used to rehearse and validate patches
+  using [GitHub CI infrastructure][build-status].
+
+<a name="emacscore"></a>
+# Contribute to Eglot's development
+
+Contributing to Eglot is done by contributing to the Emacs 
+project.  Read below for how Eglot fits in and how to quickly
+[submit a patch](#submitpatch).
+
+## Understanding :core packages
+
+From a development perspective, moving to core allows us to work on
+Eglot in tandem with other related packages already in Emacs, such as
+[Flymake][flymake], [ElDoc][eldoc], [Xref][xref], [Project][project].
+
+This means adding or tweaking an Emacs LSP feature is a matter of
+submitting a single patch to Emacs targetting multiple relevant 
+packages, not just Eglot.  You may even propose a new package 
+altogether.
+
+These -- Eglot included -- are so-called `:core` packages.  They 
+are released periodically to GNU ELPA, so users of older Emacs
+versions can get all the googies via `M-x package-install`.
+
+<a name="submitpatch"></a>
+## Actualy submitting a patch
+
+The recommended way to experiment with changes the code is to
+compile Emacs from a Git repo like 
+[this one](https://cgit.git.savannah.gnu.org/cgit/emacs.git)
+or [this one](https://github.com/emacs-mirror/emacs).  Here are 
+[three][compile-emacs1] [separate][compile-emacs2]
+[guides][compile-emacs3-official] for doing so.
+
+When you are content with your tweaks to Eglot (and/or its sibling 
+`:core` packages), submit you patch **💪via email💪** to 
+`bug-gnu-emacs@gnu.org`.  You may CC the authors/maintainers of 
+packages if you know their emails but it isn't strictly necessary.
+We'll guide you if any more steps are needed (like copyright 
+assignments, etc).
+
 <a name="animated_gifs"></a>
 # _Obligatory animated gif section_