Context Navigation

Changes between Version 1 and Version 2 of Ticket #12387, comment 11

-                      v1
+                      v2
 Any skin is not set up in a CKEditor until we create the first instance. When a first skin is loaded then all CSS files are loaded as well. If we would like to create a new instance with diffrent skin then we should unload a CSS files which are connected with a first skin - we don't have such mechanism. And it might break a previous CKEditor instance.
+No skin is set up in CKEditor until you create the first editor instance. When the first skin is loaded, all CSS files are loaded as well. If you wanted to create a new editor instance with a diffrent skin, you should unload the CSS files which are connected with the first skin. At the moment no such mechanism exists for CKEditor, though. This solution might also break the previous CKEditor instance.
 I you create '''first''' editor instance with custom skin everything should work well, because nothing is set up yet.
+I you create the '''first''' editor instance with a custom skin, everything should work well because nothing is set up yet.
 If you got existing instance on a page and want to create a new one with custom skin only idea is to create an instance in scope i.e. in an iframe.
+If you have an existing instance on the page and want to create a new instance with a custom skin, the only solution sems to be to create an instance in the scope i.e. in an iframe.