svn commit: r1599107 - /stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext

[rwesten]

Author: rwesten
Date: Mon Jun  2 07:58:25 2014
New Revision: 1599107

URL: http://svn.apache.org/r1599107
Log:
minor changes

Modified:
    stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext

Modified: stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext
URL: 
http://svn.apache.org/viewvc/stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext?rev=1599107&r1=1599106&r2=1599107&view=diff
==============================================================================
--- stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext (original)
+++ stanbol/site/trunk/content/docs/trunk/customvocabulary.mdtext Mon Jun  2 
07:58:25 2014
@@ -16,7 +16,7 @@ The aim of this usage scenario is to pro
 
 The following figure shows the typical Enhancement workflow that may start 
with some preprocessing steps (e.g. the conversion of rich text formats to 
plain text) followed by the Natural Language Processing phase. Next 'Semantic 
Lifting' aims to connect the results of text processing and link it to the 
application domain of the user. During Postprocessing those results may get 
further refined.
 
-<p style="text-align: center;">![Typical Enhancement 
Workflow](enhancementworkflow.png "This figure shows typical enhancement chains 
for Apache Stanbol")</p>
+![Typical Enhancement Workflow](enhancementworkflow.png "This figure shows 
typical enhancement chains for Apache Stanbol")
 
 This usage scenario is all about the Semantic Lifting phase. This phase is 
most central to for how well enhancement results to match the requirements of 
the users application domain. Users that need to process health related 
documents will need to provide vocabularies containing life science related 
entities otherwise the Stanbol Enhancer will not perform as expected on those 
documents. Similar processing Customer requests can only work if Stanbol has 
access to data managed by the CRM.