Typo fixes from rhubarbpieguy on blfs-dev

This commit is contained in:
Rahul Chandra 2023-09-21 19:02:48 -04:00
parent 850ac6f030
commit bcfaad0264
2 changed files with 4 additions and 4 deletions

View File

@ -190,7 +190,7 @@ make</userinput></screen>
</para> </para>
<para> <para>
The JIT test suite can use a large amount of system memory. The JIT test suite can use a large amount of system memory.
Running the JIT test suite without enough memory may invoke the Running the JIT test suite without enough memory may invoke
the kernel OOM killer and causes stability issues. To run the JIT test the kernel OOM killer and causes stability issues. To run the JIT test
suite, ensure the amount of available system memory is at least 16 GB, suite, ensure the amount of available system memory is at least 16 GB,
<!-- When I run it within a cgroup with 8 GB memory assigned, the test <!-- When I run it within a cgroup with 8 GB memory assigned, the test
@ -205,7 +205,7 @@ make</userinput></screen>
An issue in the installation process causes any running program which An issue in the installation process causes any running program which
links to SpiderMonkey shared library (for example, GNOME Shell) to links to SpiderMonkey shared library (for example, GNOME Shell) to
crash if SpiderMonkey is reinstalled, or upgraded or downgraded crash if SpiderMonkey is reinstalled, or upgraded or downgraded
without a change of the the major version number without a change of the major version number
(&spidermonkey-major; in &spidermonkey-version;). To work around (&spidermonkey-major; in &spidermonkey-version;). To work around
this issue, remove the old version of the SpiderMonkey shared this issue, remove the old version of the SpiderMonkey shared
library before installation: library before installation:

View File

@ -270,8 +270,8 @@ chown -v -R apache:apache /srv/www</userinput></screen>
</para> </para>
<para> <para>
There is no reason, at least for for internet facing sites, not There is no reason, at least for internet facing sites, not
to use SSL encyption. Setting up a secured website does not cost to use SSL encryption. Setting up a secured website does not cost
anything except installing one additional small tool and a few anything except installing one additional small tool and a few
minutes of configuration work. Use this guideline at minutes of configuration work. Use this guideline at
<ulink url="&blfs-wiki;/Securing_a_website"/> to create <ulink url="&blfs-wiki;/Securing_a_website"/> to create