Remove 'default' class

files/en-us/web/api/canvas_api/manipulating_video_using_canvas/index.html

@@ -139,11 +139,11 @@ <h3 id="Manipulating_the_video_frame_data">Manipulating the video frame data</h3
 
 <p>When this routine is called, the video element is displaying the most recent frame of video data, which looks like this:</p>
 
-<p><img class="default internal" src="video.png"></p>
+<p><img src="video.png"></p>
 
 <p>In line 2, that frame of video is copied into the graphics context <code>ctx1</code> of the first canvas, specifying as the height and width the values we previously saved to draw the frame at half size.  Note that you can pass the video element into the context's <code>drawImage()</code> method to draw the current video frame into the context.  The result is:</p>
 
-<p><img class="default internal" src="sourcectx.png"></p>
+<p><img src="sourcectx.png"></p>
 
 <p>Line 3 fetches a copy of the raw graphics data for the current frame of video by calling the <code>getImageData()</code> method on the first context.  This provides raw 32-bit pixel image data we can then manipulate.  Line 4 computes the number of pixels in the image by dividing the total size of the frame's image data by four.</p>
 
@@ -153,7 +153,7 @@ <h3 id="Manipulating_the_video_frame_data">Manipulating the video frame data</h3
 
 <p>The resulting image looks like this:</p>
 
-<p><img class="default internal" src="output.png"></p>
+<p><img src="output.png"></p>
 
 <p>This is done repeatedly as the video plays, so that frame after frame is processed and displayed with the chroma-key effect.</p>
 

files/en-us/web/api/console/dir/index.html

@@ -24,7 +24,7 @@
 
 <p>{{AvailableInWorkers}}</p>
 
-<p><img alt="console-dir.png" class="default internal"
+<p><img alt="console-dir.png"
     src="console-dir.png"></p>
 
 <h2 id="Syntax">Syntax</h2>

files/en-us/web/api/console/index.html

@@ -225,7 +225,7 @@ <h3 id="Timers">Timers</h3>
 
 <p>Will log the time needed by the user to dismiss the alert box, log the time to the console, wait for the user to dismiss the second alert, and then log the ending time to the console:</p>
 
-<p><img class="default internal" src="console-timelog.png"></p>
+<p><img src="console-timelog.png"></p>
 
 <p>Notice that the timer's name is displayed both when the timer is started and when it's stopped.</p>
 

files/en-us/web/api/console/timeend/index.html

@@ -46,7 +46,7 @@ <h2 id="Examples">Examples</h2>
 <p>The output from the example above shows the time taken by the user to dismiss the first
 	alert box, followed by the time it took for the user to dismiss the second alert:</p>
 
-<p><img class="default internal" src="timer_output.png"></p>
+<p><img src="timer_output.png"></p>
 
 <p>Notice that the timer's name is displayed when the timer value is logged using
 	<code>timeLog()</code> and again when it's stopped. In addition, the call to timeEnd()
@@ -63,4 +63,3 @@ <h2 id="Browser_compatibility">Browser compatibility</h2>
 
 	<p>{{Compat}}</p>
 </div>
-

files/en-us/web/api/console/timelog/index.html

@@ -63,7 +63,7 @@ <h2 id="Examples">Examples</h2>
 <p>The output from the example above shows the time taken by the user to dismiss the first
   alert box, followed by the time it took for the user to dismiss the second alert:</p>
 
-<p><img class="default internal" src="timer_output.png"></p>
+<p><img src="timer_output.png"></p>
 
 <p>Notice that the timer's name is displayed when the timer value is logged using
   <code>timeLog()</code> and again when it's stopped. In addition, the call to timeEnd()
@@ -77,4 +77,3 @@ <h2 id="Specifications">Specifications</h2>
 <h2 id="Browser_compatibility">Browser compatibility</h2>
 
 <p>{{Compat}}</p>
-

files/en-us/web/api/element/mouseenter_event/index.html

@@ -46,12 +46,12 @@ <h2 id="Usage_notes">Usage notes</h2>
 
 <h4>Behavior of <code>mouseenter</code> events:</h4>
 
-<img class="default internal" src="mouseenter.png">
+<img src="mouseenter.png">
 One <code>mouseenter</code> event is sent to each element of the hierarchy when entering them. Here 4 events are sent to the four elements of the hierarchy when the pointer reaches the text.
 
 <h4>Behavior of <code>mouseover</code> events:</h4>
 
-<img class="default internal" src="mouseover.png">
+<img src="mouseover.png">
 A single <code>mouseover</code> event is sent to the deepest element of the DOM tree, then it bubbles up the hierarchy until it is canceled by a handler or reaches the root.</div>
 
 <p>With deep hierarchies, the number of <code>mouseover</code> events sent can be quite huge and cause significant performance problems. In such cases, it is better to listen for <code>mouseenter</code> events.</p>

files/en-us/web/api/element/mouseleave_event/index.html

@@ -42,13 +42,13 @@
 
 <h4>Behavior of <code>mouseleave</code> events:</h4>
 
-<img class="default internal" src="mouseleave.png">
+<img src="mouseleave.png">
 
 <p>One <code>mouseleave</code> event is sent to each element of the hierarchy when leaving them. Here four events are sent to the four elements of the hierarchy when the pointer moves from the text to an area outside of the most outer div represented here.</p>
 
 <h4>Behavior of <code>mouseout</code> events:</h4>
 
-<img class="default internal" src="mouseout.png">
+<img src="mouseout.png">
 
 <p>One single <code>mouseout</code> event is sent to the deepest element of the DOM tree, then it bubbles up the hierarchy until it is canceled by a handler or reaches the root.</p>