svn commit: r823645 - in /websites/staging/airavata/trunk/content: ./ airavata/architecture/airavata-stakeholders.html

[bu...@apache.org]

Author: buildbot
Date: Thu Jun 28 19:46:53 2012
New Revision: 823645

Log:
Staging update by buildbot for airavata

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

Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Jun 28 19:46:53 2012
@@ -1 +1 @@
-1355132
+1355133

Modified: websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html
==============================================================================
--- websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html (original)
+++ websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html Thu Jun 28 19:46:53 2012
@@ -116,7 +116,7 @@ main users can be identified.</p>
 <p>Now let's focus on each user and how they fit into Airavata's big picture.</p>
 <h2 id="end-users">End Users</h2>
 <p><img alt="End Users" src="/airavata/architecture/user2.jpg" title="End Users" /></p>
-<p>Gateway End User is the one who will have a model code to do some scientific application. Sometimes this End User can be a Research Scientist. He/She writes scripts to wrap the applications up and by executing those scripts, they run the scientific workflows in Super Computers. This can be called a scientific experiment. Now the Scientist might have a requirement to call multiple of these applications together and compose a workflow. That's where the Gateway Developer comes into the picture.</p>
+<p>End User is the one who will have a model code to do some scientific application. Sometimes this End User can be a Research Scientist. He/She writes scripts to wrap the applications up and by executing those scripts, they run the scientific workflows in Super Computers. This can be called a scientific experiment. Now the Scientist might have a requirement to call multiple of these applications together and compose a workflow. That's where the Gateway Developer comes into the picture.</p>
 <h2 id="gateway-developers">Gateway Developers</h2>
 <p><img alt="Gateway Developers" src="/airavata/architecture/user3.jpg" title="Gateway Developers" /></p>
 <p>The Research Scientist is the one who comes up with requirement of bundling scienitific applications together and composing as a workflow.</p>