Updated docs.

build.html

@@ -354,6 +354,8 @@ instead) inside different build system.</p>
 <a class="reference external" href="https://github.com/floooh/fips#fips">https://github.com/floooh/fips#fips</a></p>
 <p><strong>mkvfx</strong> is a tool that builds open source libraries commonly used in games, film, and vfx.
 <a class="reference external" href="https://github.com/meshula/mkvfx#mkvfx---make-vfx-libraries-and-programs">https://github.com/meshula/mkvfx#mkvfx—make-vfx-libraries-and-programs</a></p>
+<p><strong>Conan</strong> package
+<a class="reference external" href="https://github.com/firefalcom/bgfx-conan">https://github.com/firefalcom/bgfx-conan</a></p>
 </div>
 <div class="section" id="minimal-example-without-bgfx-example-harness">
 <h2>Minimal example without bgfx’ example harness<a class="headerlink" href="#minimal-example-without-bgfx-example-harness" title="Permalink to this headline">¶</a></h2>

internals.html

@@ -169,7 +169,7 @@
 <h1>Internals<a class="headerlink" href="#internals" title="Permalink to this headline">¶</a></h1>
 <div class="section" id="sort-based-draw-call-bucketing">
 <h2>Sort based draw call bucketing<a class="headerlink" href="#sort-based-draw-call-bucketing" title="Permalink to this headline">¶</a></h2>
-<p>bgfx is using sort-based draw call bucketing. This means that submission order doesn’t necessarily match the rendering order, but on the low-level they will be sorted and ordered correctly. On the high level bgfx uses declarative API and internal sorting allows more optimal way of submitting draw calls for all passes at one place, and on the low-level this allows better optimization of rendering order. This sometimes creates undesired results usually for GUI rendering, where draw order should usually match submit order. bgfx provides way to enable sequential rendering for these cases (see <code class="docutils literal notranslate"><span class="pre">bgfx::setViewMode</span></code>).</p>
+<p>bgfx is using sort-based draw call bucketing. This means that submission order doesn’t necessarily match the rendering order, but on the low-level they will be sorted and ordered correctly. On the high level bgfx uses <strong>declarative API</strong> and internal sorting allows more optimal way of submitting draw calls for all passes at one place, and on the low-level this allows better optimization of rendering order. This sometimes creates undesired results usually for GUI rendering, where draw order should usually match submit order. bgfx provides way to enable sequential rendering for these cases (see <code class="docutils literal notranslate"><span class="pre">bgfx::setViewMode</span></code>).</p>
 <blockquote>
 <div><ul class="simple">
 <li><p>More detailed description of sort-based draw call bucketing can be found at: <a class="reference external" href="http://realtimecollisiondetection.net/blog/?p=86">Order your graphics draw calls around!</a></p></li>