Of course, as soon as you see such typos in our code, you can be 90% sure they are...
authorHermès Bélusca-Maïto <hermes.belusca-maito@reactos.org>
Wed, 14 Sep 2016 22:51:55 +0000 (22:51 +0000)
committerHermès Bélusca-Maïto <hermes.belusca-maito@reactos.org>
Wed, 14 Sep 2016 22:51:55 +0000 (22:51 +0000)
commit368cd76efb0dfa249f21d5a3e9d88c1359bac4a0
tree30b6cccaa4394652bbadc93d6d3506f6c08f084e
parenta957a1d35d7495c7d38447f9d990d3ac503b480c
Of course, as soon as you see such typos in our code, you can be 90% sure they are repeated elsewhere. And indeed they are. Fix the typos in our code (I leave them in the 3rd party code).
Concerning the fix in the NDK header I've checked that publicly available information about this structure (NirSoft website, Windows Internals book, Windows symbols...) has the member correctly named.

svn path=/trunk/; revision=72679
reactos/base/system/winlogon/lang/pt-BR.rc
reactos/drivers/bus/pcix/pci/config.c
reactos/drivers/usb/usbehci/hardware.cpp
reactos/drivers/usb/usbohci/hardware.cpp
reactos/drivers/usb/usbuhci/hardware.cpp
reactos/media/inf/kscaptur.inf
reactos/sdk/include/ndk/pstypes.h
reactos/win32ss/gdi/gdi32/misc/gdientry.c