Update README.rdoc

README.rdoc

@@ -23,18 +23,18 @@ compatible with SWFObject 2.2.  The only two significant changes to the API:
 Example:
 
 OLD:
-swfobject.embedSWF("myContent.swf", "my-target-element", "300", "120", "10.0.0");
+    swfobject.embedSWF("myContent.swf", "my-target-element", "300", "120", "10.0.0");
 
 NEW:
-var el = document.getElementById("my-target-element");
-swfobject.embedSWF("myContent.swf", el, 300, 120, 10);
+    var el = document.getElementById("my-target-element");
+    swfobject.embedSWF("myContent.swf", el, 300, 120, 10);
 
 
 Another significant change: SWFObject's approach to dynamic embedding in Internet Explorer
-has been updated to use a more W3C-friendly way of creating the <object>. Because this is
+has been updated to use a more W3C-friendly way of creating the `<object>`. Because this is
 Internet Explorer, a few hacks were required, but the end result is code generated by W3C
-techniques (document.createElement). This means, among other things, that nodes generated 
-for XHTML documents should properly self close (e.g. <object><param /></object> instead of
-<object><param></object>). Similarly, since the param elements are all generated using the
+techniques (`document.createElement`). This means, among other things, that nodes generated 
+for XHTML documents should properly self close (e.g. `<object><param /></object>` instead of
+`<object><param></object>`). Similarly, since the `<param>` elements are all generated using the
 same W3C techniques, encoding flashvars should be less troublesome. Developers will no 
-longer need to create separate workflows for IE and non-IE browsers.
+longer need to create separate flashvars encoding workflows for IE and non-IE browsers.