Use https protocol.

2 files changed, 2 insertions, 2 deletions

diff --git a/freetype2/docs/ft2faq.html b/freetype2/docs/ft2faq.html
index b0bf2b5..aac9fa3 100644
--- a/freetype2/docs/ft2faq.html
+++ b/freetype2/docs/ft2faq.html
@@ -381,7 +381,7 @@
       font files with small code size and very low memory usage.</p>
 
       <p>A good, freely available font editor is <a
-      href="http://fontforge.github.io">FontForge</a>.</p>
+      href="https://fontforge.github.io">FontForge</a>.</p>
 
       <p><a href="#top"
             class="index">
diff --git a/ttfautohint/doc/ttfautohint.html b/ttfautohint/doc/ttfautohint.html
index 38d9465..6d0b2ab 100644
--- a/ttfautohint/doc/ttfautohint.html
+++ b/ttfautohint/doc/ttfautohint.html
@@ -348,7 +348,7 @@
 <h2 id="smooth-hinting">‘Smooth’ hinting</h2>
 <p>Fundamentally, there are two approaches to hinting. The older approach, let’s call it ‘sharp’, popular when text was rendered in pure black-and-white, was to make all stems round to full pixels so that in a text line, all stems would be either one pixel or (at a larger point size) two pixels. When grayscale antialiasing came about, this approach actually started harming the rendering rather than helping it, because the horizontal and vertical stems would render very dark but round or diagonal stems would render very light.</p>
 <p>So a new approach was developed, let’s call it ‘fuzzy’, where all stems and other elements are equalized so that in grayscale (or ClearType) rendering, they all are of roughly equal color. This means that stems are not rounded to full pixels but in fact to fractions of a pixel. However, with black-and-white renderers, this approach yields poor results because in black-and-white you cannot render a fraction of a pixel, so some stems become one pixel and some become two.</p>
-<p>The TrueType auto-hinters in <a href="http://fontforge.github.io">FontForge</a> and <a href="https://www.fontlab.com/font-editor/fontlab-studio">FontLab Studio</a>, to name two well-known font editors, take the ‘sharp’ approach, while the TrueType auto-hinter in ttfautohint takes the ‘fuzzy’ approach.</p>
+<p>The TrueType auto-hinters in <a href="https://fontforge.github.io">FontForge</a> and <a href="https://www.fontlab.com/font-editor/fontlab-studio">FontLab Studio</a>, to name two well-known font editors, take the ‘sharp’ approach, while the TrueType auto-hinter in ttfautohint takes the ‘fuzzy’ approach.</p>
 <p>In theory, a hybrid approach is possible, using TrueType conditional hints: If the rasterizer is black-and-white, ‘sharp’ rendering could happen, while if the rasterizer is ClearType, the ‘fuzzy’ rendering could be used. It is not intended to add black-and-white auto-hinting to ttfautohint. However, it is planned to develop an interface so that ttfautohint can cooperate with font editors, providing this hybrid hinting.</p>
 <h1 id="ttfautohint-and-ttfautohintgui"><code>ttfautohint</code> and <code>ttfautohintGUI</code></h1>
 <p>On all supported platforms (GNU/Linux, Windows, and Mac OS X), the GUI looks quite similar; the used toolkit is <a href="https://qt.io">Qt</a>, which in turn uses the platform’s native widgets.</p>