1
0
mirror of https://github.com/samba-team/samba.git synced 2025-01-08 21:18:16 +03:00

docs-xml: Fix spelling

Signed-off-by: Joseph Sutton <josephsutton@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>
This commit is contained in:
Joseph Sutton 2023-09-04 12:14:58 +12:00 committed by Andrew Bartlett
parent c62491473a
commit f6ff6f7cdf
8 changed files with 15 additions and 15 deletions

View File

@ -1504,7 +1504,7 @@ Adds a new keytab entry, the entry can be either;
</para>
<para>
Unlike old versions no computer AD objects are modified by this command. To
preserve the bevhaviour of older clients 'net ads keytab ad_update_ads' is
preserve the behaviour of older clients 'net ads keytab ad_update_ads' is
available.
</para>
</refsect2>
@ -1514,7 +1514,7 @@ available.
<para>
Adds a new keytab entry (see section for net ads keytab add). In addition to
adding entries to the keytab file corrosponding Windows SPNs are created
adding entries to the keytab file corresponding Windows SPNs are created
from the entry passed to this command. These SPN(s) added to the AD computer
account object associated with the client machine running this command for
the following entry types;

View File

@ -132,14 +132,14 @@
<quote>KEYRING:persistent:UID</quote>, which uses the Linux
kernel keyring to store credentials on a per-UID basis.
The KEYRING has its limitations. As it is secure kernel memory,
for example bulk sorage of credentils is for not possible.</para>
for example bulk storage of credentials is not possible.</para>
<para>When using th KCM type, the supported mechanism is
<para>When using the KCM type, the supported mechanism is
<quote>KCM:UID</quote>, which uses a Kerberos credential
manaager to store credentials on a per-UID basis similar to
manager to store credentials on a per-UID basis similar to
KEYRING. This is the recommended choice on latest Linux
distributions, offering a Kerberos Credential Manager. If not
we suggest to use KEYRING as those are the most secure and
we suggest to use KEYRING as that is the most secure and
predictable method.</para>
<para>It is also possible to define custom filepaths and use the "%u"

View File

@ -26,7 +26,7 @@
<command>samba</command> process that invokes
<command>smbd</command> will still provide its normal DCERPC
services, not <command>samba-dcerpcd</command>. When
separately invoked by system startup scripts or a a daemon,
separately invoked by system startup scripts or a daemon,
the global smb.conf option <smbconfoption name="rpc start on
demand helpers">false</smbconfoption> MUST be set to allow
<command>samba-dcerpcd</command> to start standalone.

View File

@ -126,7 +126,7 @@
<varlistentry>
<term>--description=DESCRIPTION</term>
<listitem><para>
The new computers's description.
The new computer's description.
</para></listitem>
</varlistentry>
@ -246,7 +246,7 @@
<varlistentry>
<term>--description=DESCRIPTION</term>
<listitem><para>
The new contacts's description.
The new contact's description.
</para></listitem>
</varlistentry>

View File

@ -171,11 +171,11 @@
<term>fileid:nolock_max_slots = NUMBER(1-18446744073709551615)</term>
<listitem>
<para>This option alters the behavior of the <command>nolock</command> algorithm
in a ways that it also breaks the lock coherency between individual processes
in a way that it also breaks the lock coherency between individual processes
on the same host. The default is to have just 1 concurrent slot available per host.
By incressing the number of slots you can specify how many concurrent processes
By increasing the number of slots you can specify how many concurrent processes
can work on a given inode without contention, the number should typically be larger
than the a number of logical cpus, maybe 2 times of num_cpus.
than the number of logical cpus, maybe 2 times num_cpus.
</para>
</listitem>
</varlistentry>

View File

@ -168,7 +168,7 @@
<listitem>
<para>Controls where the OS X resource fork is stored.</para>
<para>Due to a spelling bug in all Samba versions older then
<para>Due to a spelling bug in all Samba versions older than
4.6.0, this option can also be given as
<emphasis>fruit:ressource</emphasis>, ie with two s.</para>

View File

@ -50,7 +50,7 @@
<para>Filesystem snapshots must be mounted on
specially named directories in order to be recognized by
<command>vfs_shadow_copy</command>. The snapshot mount points must
be immediate children of a the directory being shared.</para>
be immediate children of the directory being shared.</para>
<para>The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss,
where:

View File

@ -26,7 +26,7 @@
<para>
<emphasis>required</emphasis> - Kerberos
authentication will be required. There will be no
falllback to NTLM or a different alternative.
fallback to NTLM or a different alternative.
</para>
</listitem>