svn commit: r911146 - in /websites/staging/stratos/trunk/content: ./ index.html

[bu...@apache.org]

Author: buildbot
Date: Tue Jun  3 19:24:38 2014
New Revision: 911146

Log:
Staging update by buildbot for stratos

Modified:
    websites/staging/stratos/trunk/content/   (props changed)
    websites/staging/stratos/trunk/content/index.html

Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jun  3 19:24:38 2014
@@ -1 +1 @@
-1599736
+1599768

Modified: websites/staging/stratos/trunk/content/index.html
==============================================================================
--- websites/staging/stratos/trunk/content/index.html (original)
+++ websites/staging/stratos/trunk/content/index.html Tue Jun  3 19:24:38 2014
@@ -170,7 +170,7 @@
     <div class="cColContainer">
         <div class="cColLeft">
             <div class="cSection">
-            <h2>Why Should a <span>Developer</span> Care? </h2>
+            <h2>Why Should a <span>developer</span> care? </h2>
             <h3>Easy to Get Up and Running</h3>
             <p>Stratos PaaS is easy to get it up and running in quick time. A developer will be able to run and test PaaS framework on a single machine to try out.</p>
             <h3>Able to Add New Cartridges in Quick Time</h3>
@@ -179,11 +179,11 @@
             <p>The programming model is natural, and the developer does not have to change anything that he/she would do developing an on-premise application. Just develop the application and deploy onto Stratos, and you will have a multi-tenant enabled SaaS application. </p>
             </div>
             <div class="cSection">
-                <h2>Why should an <span>Enterprise</span> Care?</h2>
+                <h2>Why should an <span>enterprise</span> care?</h2>
             <p>Independent software vendors (ISV) looking to build vertical SaaS offerings can leverage Stratos PaaS as the platform of choice for delivering multi-tenanted SaaS applications with low cost and effort. Given the loosely coupled component architecture and also the extension and plug-in points, it is very easy to use Stratos PaaS in an OEM model. Given the wide variety of cartridges and infrastructure as a service (IaaS) layers that Stratos supports, it is ready to be re-deployed in multiple setups with heterogenous systems. So the ISVs can leverage the build once and deploy anywhere model with Stratos. </p>
             </div>
             <div class="cSection">
-            <h2>Who else Should Care? </h2>
+            <h2>Who else should care? </h2>
             <p>For enterprises, Stratos PaaS framework would yield the least Total Cost of Ownership (TCO). The key here is the in-container multi-tenancy model, where the resource utilization is maximized across tenants. Also the setup, maintenance and DevOps cost are minimal with Stratos, thanks to the unique architecture that makes DevOps effortless. An enterprise can  run and maintain the PaaS to suite and cater for multiple audiences using the polyglot cartridges model, where it can support multiple databases, programming languages, frameworks, operating systems and even legacy systems.</p>
             </div>
         </div>