Re: proposed changes to debian-faq
I very much appreciate your work on debian-faq!
Justin: thanks for your comments against this patch!
Beatrice Torracca <email@example.com> wrote:
> I updated the Italian translation of the Debian FAQ. In doing so I
> notice a couple of minor things that I think can be changed (nothing
> Since Holger is doing such an extensive great job in
> reorganizing/updating the FAQ I thought this might be a good moment to
> re-read the FAQs as a "low-level" reviewer. The changes I propose are
> mostly minor typos and such.
Great. You found a lot of typos / potential for improvement.
> The only change related to actual contents is about the use of
> I attach a suggested patch for 4 of the sgml files in the source tree.
> Holger can decide what to change or not change of course.
I would not vote myself as the main decision-maker though :-)
Always appreciating review / comments / acknowledgement / objections by
the team. Especially since I am also not a native English speaker.
And no DD (but my application is running :-) ).
> I plan to read the rest of the files in the repo too, unless someone
> objects to my suggestions.
Yes! Please do!
Some comments on your patch:
> <p>Starting with Debian Jessie, some frequently used
> -<prgn/apt-get/ and <prgn/apt-cache/ commands got an equivalent via
> +<prgn/apt-get/ and <prgn/apt-cache/ commands have an equivalent via
I don't see the improvement here, so omitting this.
> the new <prgn/apt/ binary. This means some popular commands like
> <prgn/apt-get update/, <prgn/apt-get install/, <prgn/apt-get remove/,
> <prgn/apt-cache search/, or <prgn/apt-cache show/ now can also be called
> @@ -321,8 +321,8 @@
> status symbol (explained in the header), the package name, the version
> which is <em>installed</em>, and a brief description.
> -<p>To learn the status of packages whose names match the string any
> -pattern beginning with "foo" by executing the command:
> +<p>To learn the status of packages whose names match any
> +pattern beginning with "foo", run the command:
Maybe we should change "learn" into something like "query" here?
> <example>dpkg --list 'foo*'</example>
> <p>To get a more verbose report for a particular package, execute the
> @@ -1,8 +1,8 @@
> -<!-- retain these comments for translator revision tracking -->
> +vn<!-- retain these comments for translator revision tracking -->
> <!-- Original version: $Revision: 1.24 $ -->
> <chapt id="uptodate">Keeping your Debian system up-to-date
> -<p>A Debian goal is to provide a consistent upgrade path and a secure
> +<p>One of Debian goals is to provide a consistent upgrade path and a secure
Maybe better "One of Debian's goals ... " ?
> upgrade process. We always do our best to make upgrading to new releases
> a smooth procedure. In case there's some important note to
> add to the upgrade process, the packages will alert the user, and often
> @@ -47,10 +47,19 @@
> name of a faster Debian mirror near you. See the mirror list at
> <url id="http://www.debian.org/mirror/list"> for more information.
> +<!-- info on httpredir mostly from http://httpredir.debian.org/ -->
> +<p>Or you can use the redirector httpredir.debian.org which aims to
Or you can use the redirector service httpredir.debian.org ?
(add "service" )
> + solve the problem of choosing a Debian mirror. It uses the geographic
> + location of the user and other information to choose the best mirror
> + that can serve the files. To take advantage of it use a source like
> + this one:
> +<example>http://httpredir.debian.org/debian stable main contrib non-free</example>
Maybe we should not include "non-free" in such examples?
Users may copy them directly to their sources.list and have non-free
without knowing of the exact details regarding non-free.
There is another code example in this chapter, which also includes
non-free. I would remove it there too.
> <p>More details on this can be found in the <manref name="sources.list"
> section="5"> manual page.
> -<p>To update your system in command line, run
> +<p>To update your system from the command line, run
> <example>aptitude update</example>
> followed by
> <example>aptitude full-upgrade</example>
All the rest of the patch is perfectly fine with me
(apart from the issues brought up by Justin, of course).
If noone objects, I will commit it in a week or two.
Created with Sylpheed 3.5.0 under
D E B I A N L I N U X 8 . 0 " J E S S I E " .
Registered Linux User #311290 - https://linuxcounter.net/