nightmorph    08/02/24 09:10:03

  Modified:             fluxbox-config.xml
  Log:
  fix a few small typos, no real content change

Revision  Changes    Path
1.30                 xml/htdocs/doc/en/fluxbox-config.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?rev=1.30&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?rev=1.30&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?r1=1.29&r2=1.30

Index: fluxbox-config.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v
retrieving revision 1.29
retrieving revision 1.30
diff -u -r1.29 -r1.30
--- fluxbox-config.xml  24 Feb 2008 08:22:03 -0000      1.29
+++ fluxbox-config.xml  24 Feb 2008 09:10:03 -0000      1.30
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v 1.29 
2008/02/24 08:22:03 nightmorph Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v 1.30 
2008/02/24 09:10:03 nightmorph Exp $ -->
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
 <guide link="/doc/en/fluxbox-config.xml">
@@ -58,7 +58,7 @@
 manager, simply does not have the flexibility they need, but that Fluxbox does
 not have all the built-in applications and integration they desire from a
 complete desktop environment. Thus, a person could use Fluxbox to manage the
-windows and GNOME for the rest. Note, however, that with this setup there is
+windows and GNOME for the rest. Note, however, that with this setup there are
 some issues caused by overlapping feature sets.
 </p>
 
@@ -88,17 +88,17 @@
 <p>
 Gentoo provides an ebuild to quickly and easily install Fluxbox. While Gentoo
 provides the <c>gnome</c> and <c>kde</c> USE flags to give compatibility with
-these WMs, it has been the author's experience that these USE flags are not
-needed. If you desire qt, gtk+, or any KDE/GNOME utility then you are free to
-emerge and configure those independently. For example, the author uses Fluxbox
-with <c>k3b</c>, the KDE optical disc burning utility.
+these environments, it has been the author's experience that these USE flags 
are
+not needed. If you desire qt, gtk+, or any KDE/GNOME utility then you are free
+to emerge and configure those independently. For example, the author uses
+Fluxbox with <c>k3b</c>, the KDE optical disc burning utility.
 </p>
 
 <p>
 It is also necessary to have a program lock the X display to prevent
-unauthorized access, so it would be wise to also emerge <c>xlock</c>. The vast
-majority of users will also want the ability to set their own background, so we
-will emerge <c>eterm</c>, which doubles as a nice X11 terminal.
+unauthorized access, so it would be wise to also emerge <c>xlockmore</c>. The
+vast majority of users will also want the ability to set their own background,
+so we will emerge <c>eterm</c>, which doubles as a nice X11 terminal.
 </p>
 
 <pre caption="Emerging Fluxbox">



-- 
[email protected] mailing list

Reply via email to