Refactored readability.js expected files to match readability.php style

1 files changed, 1 insertions, 3 deletions

diff --git a/test/test-pages/002/expected.html b/test/test-pages/002/expected.html
index d1837ba..504ba86 100644
--- a/test/test-pages/002/expected.html
+++ b/test/test-pages/002/expected.html
@@ -1,4 +1,3 @@
-<div id="readability-page-1" class="page">
     <article class="post" role="article">
         <p>For more than a decade the Web has used XMLHttpRequest (XHR) to achieve asynchronous requests in JavaScript. While very useful, XHR is not a very nice API. It suffers from lack of separation of concerns. The input, output and state are all managed by interacting with one object, and state is tracked using events. Also, the event-based model doesn’t play well with JavaScript’s recent focus on Promise- and generator-based asynchronous programming.</p>
         <p>The <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API">Fetch API</a> intends to fix most of these problems. It does this by introducing the same primitives to JS that are used in the HTTP protocol. In addition, it introduces a utility function <code>fetch()</code> that succinctly captures the intention of retrieving a resource from the network.</p>
@@ -382,5 +381,4 @@ res.<span>text</span><span>(</span><span>)</span>.<span>catch</span><span>(</spa
         <p>For a better web!</p>
         <p><em>The author would like to thank Andrea Marchesini, Anne van Kesteren and Ben<br/>
 Kelly for helping with the specification and implementation.</em> </p>
-    </article>
-</div>
+    </article>
\ No newline at end of file