[gnome-user-docs/wip/system-admin-guide] disk-busy.page and disk-connection-unavailable.page updated according to a review.

[Jana Svarova <jsvarova src gnome org>]

commit 86b27dba0d948c166f58c8f2a529858be37b16c8
Author: Jana Svarova <jsvarova redhat com>
Date:   Mon Sep 2 18:22:42 2013 +0200

    disk-busy.page and disk-connection-unavailable.page
    updated according to a review.

 system-admin-guide/C/disk-busy.page                |   33 +++++++++++++------
 .../C/disk-connection-unavailable.page             |   22 +++++++++---
 2 files changed, 38 insertions(+), 17 deletions(-)
---
diff --git a/system-admin-guide/C/disk-busy.page b/system-admin-guide/C/disk-busy.page
index 6617f56..7fec7a4 100644
--- a/system-admin-guide/C/disk-busy.page
+++ b/system-admin-guide/C/disk-busy.page
@@ -14,22 +14,33 @@
     <desc>What if my disk is busy?</desc>
   </info>
 
-  <title>Busy disk</title>
+  <title>What shall I do if my disk is busy?</title>
 
   <p>If you receive a notification about your disk being busy, find the
-  program/programs that keep the disk busy. All the programs currently running
-  on your computer can be found in <app>System Monitor</app> (you get to 
-  <app>System Monitor</app> by typing it in the <gui>Activities</gui> overview).</p>
-<!-- Is it true? Does the sysadmin receive a notification?
+  program/programs that keep the disk busy. Then, you may regularly end the
+  programs you are running and wait for the disk to recover. Or, you
+  can open the <gui>System Monitor</gui> and kill the program/programs.
+  Where and how can you do it?</p>
+
+  <!--Is it true? Does the sysadmin receive a notification?
 Or does he find out from, e.g.: the desktop running slowly?-->
 
-  <p>Here are a few possible solutions what you, as a system administrator, can do.</p>
+  <p>There are three different ways, two static and one interactive, of viewing
+  system processes in the terminal:</p>
+  <list>
+  <item><p>Run the <cmd>ps ax</cmd> command that shows the list of currently
+  running processes.</p></item>
+  <item><p>To display the owner of each process, use the
+  <cmd>ps aux</cmd> command.</p></item>
+  <item><p>The <cmd>top</cmd> command displays currently running processes and
+  important information about them including their memory and CPU usage.
+  This list is the only one that is both real-time and interactive.</p></item>
+  </list>
+
+  <p>Alternatively, you can go to
+  <guiseq><gui>Activities</gui><gui>System Monitor</gui></guiseq> which opens
+  a graphical interface and shows the running processes in the very first tab.</p>
 
-<list>
-  <title>Possible solutions:</title>
-  <item><p>End regularly the programs you are running and wait for the disk to recover.</p></item>
-  <item><p>Open the System Monitor and kill the program/programs that keep your disk busy.</p></item>
-</list>
 <!--Are there any other solutions?
 Can the sysadmin find some stats to find out how busy the given disk is?-->
 </page>
diff --git a/system-admin-guide/C/disk-connection-unavailable.page 
b/system-admin-guide/C/disk-connection-unavailable.page
index 03423d3..da4678c 100644
--- a/system-admin-guide/C/disk-connection-unavailable.page
+++ b/system-admin-guide/C/disk-connection-unavailable.page
@@ -11,14 +11,24 @@
       <years>2013</years>
     </credit>
 
-    <desc>Net connection is not available after suspend/resume connection or
-    connectivity loss</desc>
+    <desc>Connection to remote share/file system resource is not available after
+    suspend/resume connection or connectivity loss.</desc>
   </info>
 
-  <title>Unavailable connection</title>
+  <title>I have lost connection</title>
 
-  <p>This is a known-issue which also occurs when the user is inactive for some
-  time. The only solution is to unmount and mount again the file system, which
-  should reconnect the desktop to the net.</p>
+  <p>There is a number of situations in which the client is unexpectedly and
+  unwillingly disconnected from a "virtual file system" (or a "remote disk"),
+  is not connected again, and error messages are returned.
+  Among these situations are:</p>
+<list>
+  <item><p>the connection is interrupted (for example your notebook is
+  disconnected from the wi-fi)</p></item>
+  <item><p>the user is inactive for some time</p></item>
+  <item><p>sleeping mode is activated</p></item>
+</list>
+
+  <p>The only solution to such cases is to unmount and mount again the file
+  system, which reconnects the desktop to the source.</p>
 
 </page>