summaryrefslogtreecommitdiff
path: root/man/systemd.net-naming-scheme.xml
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2020-10-24 12:07:19 +0900
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2020-10-24 13:29:31 +0200
commit377a9545e9984578646f3f3bd8924e4dd61b905f (patch)
treed36dedc1f282323479314853193608126036265a /man/systemd.net-naming-scheme.xml
parent5a8775bb39526696d01d0e2ffd64e9509644fff1 (diff)
downloadsystemd-377a9545e9984578646f3f3bd8924e4dd61b905f.tar.gz
tree-wide: fix typos found by Fossies codespell report
Diffstat (limited to 'man/systemd.net-naming-scheme.xml')
-rw-r--r--man/systemd.net-naming-scheme.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd.net-naming-scheme.xml b/man/systemd.net-naming-scheme.xml
index e894db7cd6..6efb5be2fb 100644
--- a/man/systemd.net-naming-scheme.xml
+++ b/man/systemd.net-naming-scheme.xml
@@ -362,7 +362,7 @@
<varlistentry>
<term><constant>v247</constant></term>
- <listitem><para>If the PCI slot is assocated with PCI bridge and that has multiple child network
+ <listitem><para>If the PCI slot is associated with PCI bridge and that has multiple child network
controllers then all of them might derive the same value of <varname>ID_NET_NAME_SLOT</varname>
property. That could cause naming conflict if the property is selected as a device name. Now, we detect the
situation, slot - bridge relation, and we don't produce the <varname>ID_NET_NAME_SLOT</varname> property to