Re: Add "Editing" page/node (issue 60530047)

[PhilEHolmes]

Some proposed changes that help to make it easier to read, I hope.


https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi
File Documentation/web/introduction.itexi (right):

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1190
Documentation/web/introduction.itexi:1190: and how you actually
@emph{work} with these text files you may
Think it's simpler and better to say:

"But if you don't have a clear idea yet how you actually @emph{work}
with these text files"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1202
Documentation/web/introduction.itexi:1202: LilyPond isn't one monolithic
program as you may be used
one -> a single

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1203
Documentation/web/introduction.itexi:1203: from graphical notation
tools.  Instead it is a system with
graphical music notation tools.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1204
Documentation/web/introduction.itexi:1204: several independent parts.
This may seem irritating at first,
"This may seem irritating at first," -> "This may not be what you're
used to,"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1213
Documentation/web/introduction.itexi:1213: of other options, including
MIDI.
"there is a variety of other options" is grammatically correct, but
sounds odd to a native.  "there are a variety of other options" sounds
better.  Alternatively "a variety of other options are available,
including MIDI" avoids the issue.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1219
Documentation/web/introduction.itexi:1219: support you in working with
LilyPond files.
This would read better as:

It can be unnecessarily difficult editing LilyPond input with a plain
text editor, but fortunately there are a number of tools that actively
support working with LilyPond files.

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1236
Documentation/web/introduction.itexi:1236: automatic command completion
that helps you remembering
remembering -> remember

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1237
Documentation/web/introduction.itexi:1237: the available commands and
reduces misspelling errors at the
misspelling -> spelling

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1240
Documentation/web/introduction.itexi:1240: While these are quite basic
tools some programs offer you a
"While these are quite basic tools some programs offer" -> "Some other
programs offer"

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1241
Documentation/web/introduction.itexi:1241: complete editing environment
for working with LilyPond score.
score -> scores

https://codereview.appspot.com/60530047/diff/40001/Documentation/web/introduction.itexi#newcode1242
Documentation/web/introduction.itexi:1242: They may include templates
and entry palettes, may support
"may support" -> "support"

https://codereview.appspot.com/60530047/