Re: [PATCH] doc: add technical/whyperl

[Kyle Meyer <kyle@kyleam.com>]

No substantial comments, just some typos spotted while reading through.

Eric Wong <e@yhbt.net> writes:

> +As always, comments and corrections and additions welcome at

s/welcome/are welcome/ ?

> +* Predictable performance
> +
> +  While Perl is neither fast or memory-efficient, its

s/or/nor/

> +  performance and memory use are predictable and does not

s/does/do/

> +  require GC tuning by the user.
> +
> +  public-inbox is developed for (and mostly on) old
> +  hardware.  Perl was fast enough to power the web of the
> +  late 1990s, and any cheap VPS today has more than enough
> +  RAM and CPU for handling plain-text email.
> +
> +  Low hardware requirements increases the reach of our software

s/increases/increase/

> +* Integration with distros and non-Perl libraries
> +
> +  Perl modules and bindings to common libraries such as
> +  SQLite and Xapian are already distributed by many
> +  GNU/Linux distros and BSD ports.
> +
> +  There should be no need to rely on language-specific
> +  package managers such as cpan(1), those systems increase

s/, those/.  Those/

> +* Compactness and terseness
> +
> +  Less code generally means less bugs.  We try to avoid the

s/less bugs/fewer bugs/

> +* Lightweight threading
> +
> +  While lightweight threading implementations are
> +  convenient, they tend to be significantly heavier than a
> +  pure event-loop systems (or multi-threaded event-loop

s/a pure/pure/