Remove <<<--- markers like this --->>> about missing examples

These are not useful.

files/en-us/web/api/intersectionobserver/observe/index.html

@@ -31,11 +31,6 @@ <h3 id="Return_value">Return value</h3>
 
 <p><code>undefined</code>.</p>
 
-
-<h2 id="Examples">Examples</h2>
-
-<p>&lt;&lt;&lt;...&gt;&gt;&gt;</p>
-
 <h2 id="Specifications">Specifications</h2>
 
 <table class="standard-table">

files/en-us/web/api/intersectionobserver/takerecords/index.html

@@ -31,11 +31,6 @@ <h3 id="Return_value">Return value</h3>
 
 <p>An array of {{domxref("IntersectionObserverEntry")}} objects, one for each target element whose intersection with the root has changed since the last time the intersections were checked.</p>
 
-
-<h2 id="Examples">Examples</h2>
-
-<p>&lt;&lt;&lt;...&gt;&gt;&gt;</p>
-
 <h2 id="Specifications">Specifications</h2>
 
 <table class="standard-table">

files/en-us/web/api/intersectionobserver/thresholds/index.html

@@ -32,10 +32,6 @@ <h3 id="Value">Value</h3>
 <p>Be careful! Although the <code>options</code> object you can specify when creating an {{domxref("IntersectionObserver")}} has a field named {{domxref("IntersectionObserver.threshold", "threshold")}}, this property is called <code>thresholds</code>. Confusing? Yes. If you accidentally use <code>thresholds</code> as the name of the field in your <code>options</code>, the <code>thresholds</code> array will wind up being simply <code>[0.0]</code>, which is likely not what you expect. Debugging chaos may ensue.</p>
 </div>
 
-<h2 id="Examples">Examples</h2>
-
-<p>&lt;&lt;&lt;...&gt;&gt;&gt;</p>
-
 <h2 id="Specifications">Specifications</h2>
 
 <table class="standard-table">

files/en-us/web/api/rtcremoteoutboundrtpstreamstats/reportssent/index.html

@@ -34,10 +34,6 @@ <h2 id="Usage_notes">Usage notes</h2>
 
 <p>Sender reports, described in {{RFC(3550, "", "6.4.1")}} with an overview in {{RFC(3550, "", "6.4")}}, are used by RTP to share data transmission quality feedback between the two peers. The data in these reports is used by WebRTC to fill out various fields within the statistics objects, and this property's value indicates how many times that information was shared.</p>
 
-<h2 id="Examples">Examples</h2>
-
-<p><strong>&lt;&lt;&lt;--- add an example ---&gt;&gt;&gt;</strong></p>
-
 <h2 id="Browser_compatibility">Browser compatibility</h2>
 
 <p>{{Compat("api.RTCRemoteOutboundRtpStreamStats.reportsSent")}}</p>

files/en-us/web/api/webxr_device_api/bounded_reference_spaces/index.html

@@ -62,8 +62,6 @@ <h2 id="Understanding_boundaries">Understanding boundaries</h2>
 
 <p>The easiest solution is to just treat the each boundary segment as if it were an object to hit test against. As the user grows close to the boundary, you might warn them by displaying a message, flashing a warning indicator, playing an audio warning, or the like. And if the user actually collides with the boundary, don't let them continue past it.</p>
 
-<p><strong>&lt;&lt;&lt;--- example ---&gt;&gt;&gt;</strong></p>
-
 <h2 id="Creating_a_bounded_reference_space">Creating a bounded reference space</h2>
 
 <p>Before creating a project that relies on bounded reference spaces, it's important to keep in mind that not all XR devices are capable of creating them. By their very nature, bounded reference spaces have special hardware requirements, since they need to allow for the user to physically move around in space while their movements are tracked. In this section, we'll look at how to safely create a session that will work whether bounded spaces are supported or not.</p>

files/en-us/web/api/webxr_device_api/spatial_tracking/index.html

@@ -180,8 +180,6 @@ <h3 id="When_tracking_resumes">When tracking resumes</h3>
 
 <p>You can do this by creating a new reference space that incorporates into its effective origin the distance the viewer's position jumped since the previous frame, using the {{domxref("XRReferenceSpace")}} method {{domxref("XRReferenceSpace.getOffsetReferenceSpace", "getOffsetReferenceSpace()")}}.</p>
 
-<p><strong>&lt;&lt;&lt;--- needs an example ---&gt;&gt;&gt;</strong></p>
-
 <h3 id="The_reset_event">The reset event</h3>
 
 <p><strong><em>&lt;&lt;&lt;--- this section probably has problems still; corrections are appreciated ---&gt;&gt;&gt;</em></strong></p>

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

@@ -49,10 +49,6 @@ <h2 id="Properties">Properties</h2>
  <dd>A Boolean value which is <code>false</code> if the position and orientation given by {{DOMxRef("XRPose.transform", "transform")}} is obtained directly from a full six degree of freedom (6DoF) XR device (that is, a device which tracks not only the pitch, yaw, and roll of the head but also the forward, backward, and side-to-side motion of the viewer). If any component of the <code>transform</code> is computed or created artificially (such as by using mouse or keyboard controls to move through space), this value is instead <code>true</code>, indicating that the <code>transform</code> is in part emulated in software.</dd>
 </dl>
 
-<h2 id="Example">Example</h2>
-
-<p><strong>&lt;&lt;&lt;--- TODO: Needs example ---&gt;&gt;&gt;</strong></p>
-
 <h2 id="Specifications">Specifications</h2>
 
 <table class="standard-table">