ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From br...@apache.org
Subject svn commit: r1487789 - /ace/site/trunk/content/user-doc/getting-started.mdtext
Date Thu, 30 May 2013 08:54:25 GMT
Author: bramk
Date: Thu May 30 08:54:25 2013
New Revision: 1487789

URL: http://svn.apache.org/r1487789
Log:
ACE-139 Typos

Modified:
    ace/site/trunk/content/user-doc/getting-started.mdtext

Modified: ace/site/trunk/content/user-doc/getting-started.mdtext
URL: http://svn.apache.org/viewvc/ace/site/trunk/content/user-doc/getting-started.mdtext?rev=1487789&r1=1487788&r2=1487789&view=diff
==============================================================================
--- ace/site/trunk/content/user-doc/getting-started.mdtext (original)
+++ ace/site/trunk/content/user-doc/getting-started.mdtext Thu May 30 08:54:25 2013
@@ -59,9 +59,9 @@ The following steps can be followed to g
 1. Drag the distribution onto the target to associate it.
 1. Click on 'Store' to actually store changes on the server, which should trigger the actual
deployment of the artifacts to the target.
 
-## Validating that it worked
+## Validating that it works
 
-After following the steps listed above the bundles should have been provisioned onto the
target. But did it work? There are a lot of things that can go wrong the first time. For exmaple,
remember you are provisioning into an empty OSGi framework so the deployment should be able
to resolve. Two ways to debug problems are;
+After following the steps listed above the bundles should have been provisioned onto the
target. But did it work? There are a lot of things that can go wrong the first time. For example,
remember you are provisioning into an empty OSGi framework so the deployment should be able
to resolve. Two ways to debug problems are;
 
 1. Inspect state and log of the target by double-clicking it in the webui.
 1. Start of by provisioning a shell to allow inspection of the target itself.



Mime
View raw message