Fix spelling and grammar
This commit is contained in:
parent
6b0848e5a9
commit
a6d9312af0
32
about.xhtml
32
about.xhtml
@ -1,7 +1,7 @@
|
|||||||
<!DOCTYPE html>
|
<!DOCTYPE html>
|
||||||
|
|
||||||
<!-- Inferencium - Website - About -->
|
<!-- Inferencium - Website - About -->
|
||||||
<!-- Version: 10.2.0-alpha.7 -->
|
<!-- Version: 10.2.0-alpha.8 -->
|
||||||
|
|
||||||
<!-- Copyright 2022 Jake Winters -->
|
<!-- Copyright 2022 Jake Winters -->
|
||||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||||
@ -203,7 +203,7 @@
|
|||||||
<p><b>SPDX License Identifier:</b> <code>BSD-3-Clause</code></p>
|
<p><b>SPDX License Identifier:</b> <code>BSD-3-Clause</code></p>
|
||||||
<p><b>Type: Permissive</b></p>
|
<p><b>Type: Permissive</b></p>
|
||||||
<p><a href="https://spdx.org/licenses/BSD-3-Clause.html">BSD 3-Clause License</a>
|
<p><a href="https://spdx.org/licenses/BSD-3-Clause.html">BSD 3-Clause License</a>
|
||||||
is a highly permissive license which allows content licensed under it to be used in
|
is a highly-permissive license which allows content licensed under it to be used in
|
||||||
any way, whether in source or binary form, and allows sublicensing under a different
|
any way, whether in source or binary form, and allows sublicensing under a different
|
||||||
license, with the only restrictions being the original copyright notice must be kept
|
license, with the only restrictions being the original copyright notice must be kept
|
||||||
in order to attribute the original creator of the licensed content, and the name of
|
in order to attribute the original creator of the licensed content, and the name of
|
||||||
@ -274,14 +274,15 @@
|
|||||||
a period, then the version of that phase; for example, <code>-alpha.<var>n</var></code> for
|
a period, then the version of that phase; for example, <code>-alpha.<var>n</var></code> for
|
||||||
an alpha version, <code>-beta.<var>n</var></code> for a beta version, and
|
an alpha version, <code>-beta.<var>n</var></code> for a beta version, and
|
||||||
<code>-rc.<var>n</var></code> for a release candidate version, with
|
<code>-rc.<var>n</var></code> for a release candidate version, with
|
||||||
<code><var>n</var></code> being a non-negative integer. Stable versions have no suffix.</p>
|
<code><var>n</var></code> being a positive integer beginning at 1. Stable versions have no
|
||||||
|
suffix.</p>
|
||||||
</section>
|
</section>
|
||||||
<section id="versioning-phases">
|
<section id="versioning-phases">
|
||||||
<h3><a href="#versioning-phases">What Are the Phases?</a></h3>
|
<h3><a href="#versioning-phases">What Are the Phases?</a></h3>
|
||||||
<p>There are 4 phases of development. Each phase typically has its own branch in each source
|
<p>There are 4 phases of development. Each phase typically has its own branch in each source
|
||||||
code repository. The phases are as follows:</p>
|
code repository. The phases are as follows:</p>
|
||||||
<ol>
|
<ol>
|
||||||
<li>Alpha: Pre-alpha development and alpha testing occurs in this phase. Features
|
<li>Alpha: Pre-alpha development and alpha-testing occurs in this phase. Features
|
||||||
are added, modified, and/or removed. Fixes and optimisations may also occur if they
|
are added, modified, and/or removed. Fixes and optimisations may also occur if they
|
||||||
are caught during this phase. This is where the majority of changes occur and where
|
are caught during this phase. This is where the majority of changes occur and where
|
||||||
the fine-grained commits can be found. Breakage is highly likely within this phase
|
the fine-grained commits can be found. Breakage is highly likely within this phase
|
||||||
@ -316,8 +317,9 @@
|
|||||||
<section id="services">
|
<section id="services">
|
||||||
<h2><a href="#services">Services</a></h2>
|
<h2><a href="#services">Services</a></h2>
|
||||||
<p>This list contains the policies and practices of my services.</p>
|
<p>This list contains the policies and practices of my services.</p>
|
||||||
<p>My policies and practices are heavily security- and privacy-focused, with improvements made on an
|
<p>My policies and practices are heavily security-focused and privacy-focused, with improvements
|
||||||
ongoing basis as new technologies, protocols, and software become available.</p>
|
made on an ongoing basis as new technologies, hardware, software, and protocols become
|
||||||
|
available.</p>
|
||||||
<h3 id="services-websites"><a href="#services-websites">Websites</a></h3>
|
<h3 id="services-websites"><a href="#services-websites">Websites</a></h3>
|
||||||
<ul>
|
<ul>
|
||||||
<li>Unnecessary logging avoided (only logs required for security and debugging
|
<li>Unnecessary logging avoided (only logs required for security and debugging
|
||||||
@ -332,8 +334,8 @@
|
|||||||
ciphers are used, along with
|
ciphers are used, along with
|
||||||
<a href="https://en.wikipedia.org/wiki/Forward_secrecy">forward secrecy</a></li>
|
<a href="https://en.wikipedia.org/wiki/Forward_secrecy">forward secrecy</a></li>
|
||||||
<li>All connections made via high-security AEAD ciphers, preferring AES-256-GCM for
|
<li>All connections made via high-security AEAD ciphers, preferring AES-256-GCM for
|
||||||
devices with AES hardware acceleration, and ChaCha20-Poly1305 for devices without AES
|
devices with AES hardware-acceleration, and ChaCha20-Poly1305 for devices without AES
|
||||||
hardware acceleration, with AES-128-GCM as a fallback (AES-128-GCM is mandated for TLS
|
hardware-acceleration, with AES-128-GCM as a fallback (AES-128-GCM is mandated for TLS
|
||||||
1.3 by
|
1.3 by
|
||||||
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
|
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
|
||||||
<li>All connections are made via high-security key exchange protocols, preferring
|
<li>All connections are made via high-security key exchange protocols, preferring
|
||||||
@ -502,7 +504,7 @@
|
|||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-pc-description gentoo_linux">
|
<td class="desc" headers="software-pc-description gentoo_linux">
|
||||||
<p><a href="https://www.gentoo.org/">Gentoo Linux</a>
|
<p><a href="https://www.gentoo.org/">Gentoo Linux</a>
|
||||||
is a highly modular, source-based, Linux-based operating system
|
is a highly-modular, source-based, Linux-based operating system
|
||||||
which allows vast customisation to tailor the operating system
|
which allows vast customisation to tailor the operating system
|
||||||
to suit your specific needs. There are many advantages to such
|
to suit your specific needs. There are many advantages to such
|
||||||
an operating system, with the most notable being the ability to
|
an operating system, with the most notable being the ability to
|
||||||
@ -556,7 +558,7 @@
|
|||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-pc-description chromium">
|
<td class="desc" headers="software-pc-description chromium">
|
||||||
<p><a href="https://chromium.org/">Chromium</a>
|
<p><a href="https://chromium.org/">Chromium</a>
|
||||||
is a highly secure web browser which is often ahead of other web
|
is a highly-secure web browser which is often ahead of other web
|
||||||
browsers in security aspects. It has a dedicated security team
|
browsers in security aspects. It has a dedicated security team
|
||||||
and a very impressive
|
and a very impressive
|
||||||
<a href="https://www.chromium.org/Home/chromium-security/brag-sheet/">security brag sheet</a>.
|
<a href="https://www.chromium.org/Home/chromium-security/brag-sheet/">security brag sheet</a>.
|
||||||
@ -599,9 +601,8 @@
|
|||||||
</th>
|
</th>
|
||||||
<td class="desc" headers="software-pc-description software-vcs">
|
<td class="desc" headers="software-pc-description software-vcs">
|
||||||
<p><a href="https://gitea.com/">Gitea</a>
|
<p><a href="https://gitea.com/">Gitea</a>
|
||||||
is a self-hosted, all-in-one development platform with Git
|
is an all-in-one development platform with Git hosting, code
|
||||||
hosting, code review, team collaboration, package registry and
|
review, team collaboration, package registry and CI/CD.</p>
|
||||||
CI/CD.</p>
|
|
||||||
</td>
|
</td>
|
||||||
<td headers="software-pc-source_model gitea">
|
<td headers="software-pc-source_model gitea">
|
||||||
<p>Open-source</p>
|
<p>Open-source</p>
|
||||||
@ -665,8 +666,7 @@
|
|||||||
overall high-security practices.</p>
|
overall high-security practices.</p>
|
||||||
<p>For an extensive list of features GrapheneOS provides, visit
|
<p>For an extensive list of features GrapheneOS provides, visit
|
||||||
its
|
its
|
||||||
<a href="https://grapheneos.org/features/">official features list</a>
|
<a href="https://grapheneos.org/features/">official features list</a>.
|
||||||
which provides extensive documentation.</p>
|
|
||||||
</td>
|
</td>
|
||||||
<td headers="software-smartphone-source_model grapheneos">
|
<td headers="software-smartphone-source_model grapheneos">
|
||||||
<p>Open-source</p>
|
<p>Open-source</p>
|
||||||
@ -682,7 +682,7 @@
|
|||||||
<p>Vanadium is a security-hardened, privacy-hardened,
|
<p>Vanadium is a security-hardened, privacy-hardened,
|
||||||
Chromium-based web browser which utilises GrapheneOS' operating
|
Chromium-based web browser which utilises GrapheneOS' operating
|
||||||
system hardening to implement stronger defenses to the already
|
system hardening to implement stronger defenses to the already
|
||||||
very secure Chromium web browser.</p>
|
very-secure Chromium web browser.</p>
|
||||||
<p>Its hardening alongside Chromium's base security features
|
<p>Its hardening alongside Chromium's base security features
|
||||||
includes
|
includes
|
||||||
<a href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/0081-Implement-UI-for-JIT-site-settings.patch">disabling JavaScript just-in-time (JIT) compilation by default</a>,
|
<a href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/0081-Implement-UI-for-JIT-site-settings.patch">disabling JavaScript just-in-time (JIT) compilation by default</a>,
|
||||||
|
Loading…
x
Reference in New Issue
Block a user