Skip to content

Preparing Final Report #4

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 14 commits into from
Jul 4, 2014
Next Next commit
Fixed typos that David found.
  • Loading branch information
Dominik Röttsches committed Jul 2, 2014
commit 8be327de6bd7ef36b6bfec5a7ff48d97d0795455
8 changes: 4 additions & 4 deletions Overview.src.html
Original file line number Diff line number Diff line change
Expand Up @@ -289,7 +289,7 @@ <h2>Conformance</h2>
<p>Requirements phrased in the imperative as part of algorithms
(such as "strip any leading space characters" or "return false and
terminate these steps") are to be interpreted with the meaning of the
key word ("must", "should", "may", etc) used in introducing the
key word ("must", "should", "may", etc.) used in introducing the
algorithm.

<p>Conformance requirements phrased as algorithms or specific steps
Expand Down Expand Up @@ -376,13 +376,13 @@ <h2>Display Selection and Availability</h2>
system via wired connections (e.g. HDMI, DVI etc.) as well as via
wireless technologies (e.g. MiraCast, DLNA or similar) that use a
local or personal area network as a transport mechanism. The
discovery can be performend by using operating system APIs that
discovery can be performed by using operating system APIs that
notifiy the user agent about display configuration changes or by
means of network discovery for remote display technologies that
are not handled by the operating system. In the latter case, the
user agent or the operating system that the user agent runs on may
prepare a video stream suitable for being decoded and displayed by
the wirelessly connected display.</p>
the wirelessly-connected display.</p>

<h3>Monitoring for Availability Changes</h3>

Expand Down Expand Up @@ -534,7 +534,7 @@ <h2>Security Considerations</h2>
<h2 class=no-num>References</h2>
<div id=anolis-references></div>

<h2 class=no-num>Acknowledgments</h2>
<h2 class=no-num>Acknowledgements</h2>

<p>Thanks to Wayne Carr and Anssi Kostiainen for input, thorough reviews and feedback to this draft.</p>

Expand Down
12 changes: 6 additions & 6 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
}
</style>

<link href="http://www.w3.org/community/src/css/spec/cg-final.css" rel="stylesheet" type="text/css">
<link href="http://www.w3.org/community/src/css/spec/cg-draft.css" rel="stylesheet" type="text/css">
<style type="text/css">
/* Note formatting taken from HTML5 spec */
.note { border-left-style: solid; border-left-width: 0.25em; background: none repeat scroll 0 0 #E9FBE9; border-color: #52E052; }
Expand Down Expand Up @@ -176,7 +176,7 @@ <h2 class="no-num no-toc" id="table-of-contents">Table of Contents</h2>
<li><a href="#close-on-unload"><span class="secno">8.4 </span>Close on Unload</a></ol></li>
<li><a href="#security-considerations"><span class="secno">9 </span>Security Considerations</a></li>
<li><a class="no-num" href="#references">References</a></li>
<li><a class="no-num" href="#acknowledgments">Acknowledgments</a></ol>
<li><a class="no-num" href="#acknowledgements">Acknowledgements</a></ol>
<!--end-toc-->

<h2 id="introduction"><span class="secno">1 </span>Introduction</h2>
Expand Down Expand Up @@ -314,7 +314,7 @@ <h2 id="conformance"><span class="secno">2 </span>Conformance</h2>
<p>Requirements phrased in the imperative as part of algorithms
(such as "strip any leading space characters" or "return false and
terminate these steps") are to be interpreted with the meaning of the
key word ("must", "should", "may", etc) used in introducing the
key word ("must", "should", "may", etc.) used in introducing the
algorithm.

<p>Conformance requirements phrased as algorithms or specific steps
Expand Down Expand Up @@ -398,13 +398,13 @@ <h2 id="display-selection-and-availability"><span class="secno">6 </span>Display
system via wired connections (e.g. HDMI, DVI etc.) as well as via
wireless technologies (e.g. MiraCast, DLNA or similar) that use a
local or personal area network as a transport mechanism. The
discovery can be performend by using operating system APIs that
discovery can be performed by using operating system APIs that
notifiy the user agent about display configuration changes or by
means of network discovery for remote display technologies that
are not handled by the operating system. In the latter case, the
user agent or the operating system that the user agent runs on may
prepare a video stream suitable for being decoded and displayed by
the wirelessly connected display.</p>
the wirelessly-connected display.</p>

<h3 id="monitoring-for-availability-changes"><span class="secno">6.1 </span>Monitoring for Availability Changes</h3>

Expand Down Expand Up @@ -566,7 +566,7 @@ <h2 class="no-num" id="references">References</h2>

</dl></div>

<h2 class="no-num" id="acknowledgments">Acknowledgments</h2>
<h2 class="no-num" id="acknowledgements">Acknowledgements</h2>

<p>Thanks to Wayne Carr and Anssi Kostiainen for input, thorough reviews and feedback to this draft.</p>

Expand Down