svn commit: r1600898 - /sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext

[dk...@apache.org]

Author: dklco
Date: Fri Jun  6 14:26:18 2014
New Revision: 1600898

URL: http://svn.apache.org/r1600898
Log:
Removing inline styles

Modified:
    sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext

Modified: sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext?rev=1600898&r1=1600897&r2=1600898&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext (original)
+++ sling/site/trunk/content/documentation/the-sling-engine/authentication.mdtext Fri Jun  6 14:26:18 2014
@@ -8,8 +8,8 @@ Let's look at generic request processing
 
 This method is called by the OSGi HTTP Service implementation after the servlet has been selected to handle the request but before actually calling the servlet's `service` method.
 
-<a href="authentication.png" style="float:left;padding-right:5%;width:30%;">
-    <img src="authentication.png" title="Authentication Flow" alt="Authentication Flow" width="30%">
+<a href="authentication.png" style="float:left;padding-right:5%">
+    <img src="authentication.png" title="Authentication Flow" alt="Authentication Flow" />
 </a>
 
 1. First the OSGi HTTP Service implementation is analyzing the request URL to find a match for a servlet or resource registered with the HTTP Service.