Return-Path: 
 <airavata-commits-return-2311-apmail-incubator-airavata-commits-archive=incubator.apache.org@incubator.apache.org>
X-Original-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org
Delivered-To: apmail-incubator-airavata-commits-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 69E509C51
	for <apmail-incubator-airavata-commits-archive@minotaur.apache.org>;
 Fri, 22 Jun 2012 15:57:42 +0000 (UTC)
Received: (qmail 978 invoked by uid 500); 22 Jun 2012 15:57:42 -0000
Delivered-To: apmail-incubator-airavata-commits-archive@incubator.apache.org
Received: (qmail 938 invoked by uid 500); 22 Jun 2012 15:57:42 -0000
Mailing-List: contact airavata-commits-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:airavata-commits-help@incubator.apache.org>
List-Unsubscribe: <mailto:airavata-commits-unsubscribe@incubator.apache.org>
List-Post: <mailto:airavata-commits@incubator.apache.org>
List-Id: <airavata-commits.incubator.apache.org>
Reply-To: airavata-dev@incubator.apache.org
Delivered-To: mailing list airavata-commits@incubator.apache.org
Received: (qmail 931 invoked by uid 99); 22 Jun 2012 15:57:42 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jun 2012 15:57:42 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED
X-Spam-Check-By: apache.org
Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jun 2012 15:57:41 +0000
Received: from eris.apache.org (localhost [127.0.0.1])
	by eris.apache.org (Postfix) with ESMTP id 5590723889E0
	for <airavata-commits@incubator.apache.org>;
 Fri, 22 Jun 2012 15:57:21 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r822749 - in /websites/staging/airavata/trunk/content: ./
 airavata/architecture/airavata-user.html
Date: Fri, 22 Jun 2012 15:57:21 -0000
To: airavata-commits@incubator.apache.org
From: buildbot@apache.org
X-Mailer: svnmailer-1.0.8-patched
Message-Id: <20120622155721.5590723889E0@eris.apache.org>
X-Virus-Checked: Checked by ClamAV on apache.org

Author: buildbot
Date: Fri Jun 22 15:57:20 2012
New Revision: 822749

Log:
Staging update by buildbot for airavata

Modified:
    websites/staging/airavata/trunk/content/   (props changed)
    websites/staging/airavata/trunk/content/airavata/architecture/airavata-user.html

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 22 15:57:20 2012
@@ -1 +1 @@
-1352934
+1352941

Modified: websites/staging/airavata/trunk/content/airavata/architecture/airavata-user.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/airavata-user.html (original)
+++ websites/staging/airavata/trunk/content/airavata/architecture/airavata-user.html Fri Jun 22 15:57:20 2012
@@ -19,7 +19,7 @@
     limitations under the License.
 -->
   <link href="/airavata/css/airavata.css" rel="stylesheet" type="text/css">
-  <title>Distributed Application Management</title>
+  <title></title>
   <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
 </head>
 
@@ -88,12 +88,15 @@
   </div>
 
   <div id="content">
-    <h1 class="title">Distributed Application Management</h1>
-    <p>Airavata is a toolkit which enables a user to build Science Gateways. From the standpoint of Airavata, three
-main users can be identified.
-<em> Research Scientists
-</em> Gateway Developers
-* Core Developers</p>
+    <h1 class="title"></h1>
+    <h1 id="airavata-users">Airavata Users</h1>
+<p>Airavata is a framework which enables a user to build Science Gateways. It is used to compose, manage, execute and monitor distributed applications and workflows on computational resources. These computational resources can range from local resources to computational grids and clouds. Therefore,  various users with different backgrounds either contribute or use Airavata in their  applications. From the Airavata standpoint, three
+main users can be identified.</p>
+<ul>
+<li>Research Scientists</li>
+<li>Gateway Developers</li>
+<li>Core Developers</li>
+</ul>
 <p>Now let's focus on each user and how they fit into Airavata's big picture.</p>
 <h2 id="research-scientists">Research Scientists</h2>
 <h2 id="gateway-developers">Gateway Developers</h2>