PATCH: clarify language in an example in eglot.texi

[Pedro Andres Aranda Gutierrez <paaguti@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 464 bytes --]

Hi

attached is a patch for eglot.texi. I have had several questions from
non-L1 English speakers and when I read it (being an L2 speaker), I had to
parse it twice before I got what was meant.

Just my .02 cents

-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #1.2: Type: text/html, Size: 771 bytes --]

[-- Attachment #2: 002-eglot-manual.diff --]
[-- Type: text/x-patch, Size: 898 bytes --]

diff --git a/doc/misc/eglot.texi b/doc/misc/eglot.texi
index cf9607e3b7..7c44e361f4 100644
--- a/doc/misc/eglot.texi
+++ b/doc/misc/eglot.texi
@@ -987,11 +987,10 @@ Customizing Eglot
 JSON value to be sent to the server.  This helper command works even
 before actually connecting to the server.
 
-Here's an example of defining the workspace-configuration settings for
-a project that uses two different language servers, one for Python,
-whose server is @command{pylsp}, the other one for Go, with
-@command{gopls} as its server (presumably, the project is written in a
-combination of these two languages):
+For example, in a project written in a combination of the Python and
+Go programming languages, you could use @command{pylsp} as the language
+server for Python and @command{gopls} for Go. In this case, the
+workspace-configuration settings would look like this:
 
 @lisp
 ((python-mode