1 files changed, 1 insertions, 1 deletions

diff --git a/docs/Classes/SDLCreateWindow.html b/docs/Classes/SDLCreateWindow.html
index 961640b07..2549f0f35 100644
--- a/docs/Classes/SDLCreateWindow.html
+++ b/docs/Classes/SDLCreateWindow.html
@@ -146,7 +146,7 @@
   </h3>
   
   <p>Allows an app to create a widget related to a specific service type.
-@discussion As an example if a <code>MEDIA</code> app becomes active, this app becomes audible and is allowed to play audio. Actions such as skip or play/pause will be directed to this active media app. In case of widgets, the system can provide a single <q>media</q> widget which will act as a placeholder for the active media app. It is only allowed to have one window per service type. This means that a media app can only have a single MEDIA widget. Still the app can create widgets omitting this parameter. Those widgets would be available as app specific widgets that are permanently included in the HMI. This parameter is related to widgets only. The default main window, which is pre-created during app registration, will be created based on the HMI types specified in the app registration request.</p>
+@discussion As an example if a <code>MEDIA</code> app becomes active, this app becomes audible and is allowed to play audio. Actions such as skip or play/pause will be directed to this active media app. In case of widgets, the system can provide a single &ldquo;media&rdquo; widget which will act as a placeholder for the active media app. It is only allowed to have one window per service type. This means that a media app can only have a single MEDIA widget. Still the app can create widgets omitting this parameter. Those widgets would be available as app specific widgets that are permanently included in the HMI. This parameter is related to widgets only. The default main window, which is pre-created during app registration, will be created based on the HMI types specified in the app registration request.</p>