Merge pull request #3844 from OAI/update-respec-version

Update ReSpec versions

Author: handrews

oas/latest.html

@@ -3993,7 +3993,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be present but empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They would still have access to at least the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different from hiding the path itself from the <a href="#paths-object">Paths Object</a>, because the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>

oas/v3.0.0.html

@@ -4033,7 +4033,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They’d still have access to the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the <a href="#paths-object">Paths Object</a>, so the user will not be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>

oas/v3.0.1.html

@@ -3974,7 +3974,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They’d still have access to the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the <a href="#paths-object">Paths Object</a>, so the user will not be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>

oas/v3.0.2.html

@@ -3985,7 +3985,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They’d still have access to the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different than hiding the path itself from the <a href="#paths-object">Paths Object</a>, so the user will not be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>

oas/v3.0.3.html

@@ -4021,7 +4021,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They’d still have access to the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different from hiding the path itself from the <a href="#paths-object">Paths Object</a>, because the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>

oas/v3.1.0.html

@@ -3993,7 +3993,7 @@
 <li>The <a href="#paths-object">Paths Object</a> MAY be present but empty. It may be counterintuitive, but this may tell the viewer that they got to the right place, but can’t access any documentation. They would still have access to at least the <a href="#info-object">Info Object</a> which may contain additional information regarding authentication.</li>
 <li>The <a href="#path-item-object">Path Item Object</a> MAY be empty. In this case, the viewer will be aware that the path exists, but will not be able to see any of its operations or parameters. This is different from hiding the path itself from the <a href="#paths-object">Paths Object</a>, because the user will be aware of its existence. This allows the documentation provider to finely control what the viewer can see.</li>
 </ol>
-</section></section><section><h1>Appendix A: Revision History</h1>
+</section></section><section class="appendix"><h1>Appendix A: Revision History</h1>
 <table>
 <thead>
 <tr>