summaryrefslogtreecommitdiff
path: root/general/event
diff options
context:
space:
mode:
authorBarry Golden <[email protected]>2015-08-06 20:07:53 -0700
committerBarry Golden <[email protected]>2015-08-06 20:07:53 -0700
commit7c089b4b332b8a8bd2e29672bbf4f6ee430b3e77 (patch)
tree8a7e461efc0c2e77b9cd82b3968e38fd5efef7b4 /general/event
parent9026073a419b5ef68fb46d4f7fae52dbef09dbe1 (diff)
Update README.md
Diffstat (limited to 'general/event')
-rw-r--r--general/event/ReadMe.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/general/event/ReadMe.md b/general/event/ReadMe.md
index 8b8bebaa..c091af5a 100644
--- a/general/event/ReadMe.md
+++ b/general/event/ReadMe.md
@@ -9,7 +9,7 @@ This sample demonstrates two different ways a Windows kernel-mode driver can not
There are two advantages of IRP-based approach over the event-based approach. First, the driver can send a message to the application along with the event notification. Second, the driver routines don't have to run in the context of the process that made the request. Instead, the application can send a synchronous or asynchronous (overlapped) I/O control request to the driver.
-**Note**  This sample driver is not a Plug and Play driver. This is a minimal driver meant to demonstrate a feature of the operating system. Neither this driver nor its sample programs are intended for use in a production environment. Rather, they are intended for educational purposes and as a skeleton driver.
+**Note** This sample driver is not a Plug and Play driver. This is a minimal driver meant to demonstrate a feature of the operating system. Neither this driver nor its sample programs are intended for use in a production environment. Rather, they are intended for educational purposes and as a skeleton driver.
Run the sample