diff options
| author | Dan Williams <dcbw@redhat.com> | 2010-09-25 00:34:10 -0500 |
|---|---|---|
| committer | Dan Williams <dcbw@redhat.com> | 2010-09-25 00:34:10 -0500 |
| commit | b80f31e19177d2f2d0881c3e99b608407aaec16d (patch) | |
| tree | 1b0f6fe8d2880280b3c71d70a8e670512ab7fa62 /README | |
| parent | 6f2aa8a817c3696b2ac946a1f08385fbaf3812b9 (diff) | |
| download | NetworkManager-b80f31e19177d2f2d0881c3e99b608407aaec16d.tar.gz | |
trivial: typo fixes
Sent by a Debian user to Michael Biebl. No other attribution
information available. Thanks Debian user!
Diffstat (limited to 'README')
| -rw-r--r-- | README | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -66,11 +66,11 @@ those drivers that are shipped with the upstream Linux kernel, because only those drivers can be easily fixed and debugged. ndiswrapper, vendor binary drivers, or other out-of-tree drivers may or may not work well with NetworkManager, precisely because they have not been vetted and improved by the -open-source community, and becuase problems in these drivers usually cannot +open-source community, and because problems in these drivers usually cannot be fixed. Sometimes, command-line tools like 'iwconfig' will work, but NetworkManager will -fail. This is again often due to buggy drivers, becuase these drivers simply +fail. This is again often due to buggy drivers, because these drivers simply aren't expecting the dynamic requests that NetworkManager and wpa_supplicant make. Driver bugs should be filed in the bug tracker of the distribution being run, since often distributions customize their kernel and drivers. |