Changeset View
Standalone View
chapter.xml
Context not available. | |||||
<secondary>large sites running &os;</secondary> | <secondary>large sites running &os;</secondary> | ||||
</indexterm> | </indexterm> | ||||
<para>&os;'s advanced features, proven security, and predictable | <para>&os;'s advanced features, proven security, predictable | ||||
wblock: s/and // | |||||
release cycle, as well as its permissive license have lead to | release cycle, and permissive license have led to its use as a | ||||
its use as a platform for building many commericial and open | platform for building many commercial and open source appliances, | ||||
source appliances, devices, and products, including those from | devices, and products. Many of the world's largest IT | ||||
Not Done Inline ActionsThis sentence is still way too long, and "those from" has been dropped, making it even more unclear. Please split the sentence after "products". wblock: This sentence is still way too long, and "those from" has been dropped, making it even more… | |||||
many of the world's largest IT companies:</para> | companies use &os;:</para> | ||||
<itemizedlist> | <itemizedlist> | ||||
<listitem> | <listitem> | ||||
Context not available. | |||||
from the source control <command>commit</command> | from the source control <command>commit</command> | ||||
command, which is used to bring new changes into the | command, which is used to bring new changes into the | ||||
repository). The best way of making submissions for | repository). The best way of making submissions for | ||||
review by the committers list is to use the | review is to use the &man.send-pr.1; command, which is | ||||
&man.send-pr.1; command. If something appears to be | included in releases prior to &os; 10.1, or submit | ||||
jammed in the system, then you may also reach them by | issues using the <link | ||||
sending mail to the &a.committers;.</para> | xlink:href="https://bugs.FreeBSD.org/submit/">problem | ||||
Not Done Inline ActionsThere should be no added whitespace (spaces, tabs, or line breaks) between an opening tag and the contents, or the contents and the ending tag. For links, this is particularly important because the whitespace will be shown in the link: <link ...> will render in HTML as _a link _, that is, with extra underlined whitespace. Instead, write the link like with the text up against the tags: (Note: if the whitespace is actually part of the contents, like a leading tab or space indent in a programlisting, that is fine. It is really meant to be there. But we do not add them to improve line wrapping.) wblock: There should be no added whitespace (spaces, tabs, or line breaks) between an opening tag and… | |||||
report form</link>. If a problem report has not received | |||||
Not Done Inline ActionsAs previously commented, please remove the whitespace between the opening link tag and the link description. The link description should not include the period, either. wblock: As previously commented, please remove the whitespace between the opening link tag and the link… | |||||
any attention, please engage the <link | |||||
xlink:href="&url.base;community/mailinglists.html">community | |||||
mailing lists</link>.</para> | |||||
Not Done Inline ActionsThis link has the same problem. It should be (disregarding line wrap): <link xlink:href="&url.base;community/mailinglists.html">community mailing lists</link>.</para> wblock: This link has the same problem. It should be (disregarding line wrap):
<link xlink:href="&url. | |||||
</listitem> | </listitem> | ||||
</varlistentry> | </varlistentry> | ||||
Context not available. |
s/and //