doc: fix quite a few typos within Documentation

		The flags field carries '-' by default. A 'c' indicates a

		fragment of a line. All following fragments are flagged with

		'+'. Note, that these hints about continuation lines are not

		neccessarily correct, and the stream could be interleaved with

		necessarily correct, and the stream could be interleaved with

		unrelated messages, but merging the lines in the output

		usually produces better human readable results. A similar

		logic is used internally when messages are printed to the

Description:

		The /sys/devices/.../wakeup_prevent_sleep_time_ms attribute

		contains the total time the device has been preventing

		opportunistic transitions to sleep states from occuring.

		opportunistic transitions to sleep states from occurring.

		This attribute is read-only.  If the device is not enabled to

		wake up the system from sleep states, this attribute is not

		present.

Description:

		This folder includes the attributes related with PPI (Physical

		Presence Interface). Only if TPM is supported by BIOS, this

		folder makes sence. The folder path can be got by command

		folder makes sense. The folder path can be got by command

		'find /sys/ -name 'pcrs''. For the detail information of PPI,

		please refer to the PPI specification from

		http://www.trustedcomputinggroup.org/

   leaving the cpu domain and flushing caches at fault time. Note that all the

   dma_buf files share the same anon inode, hence the exporter needs to replace

   the dma_buf file stored in vma->vm_file with it's own if pte shootdown is

   requred. This is because the kernel uses the underlying inode's address_space

   required. This is because the kernel uses the underlying inode's address_space

   for vma tracking (and hence pte tracking at shootdown time with

   unmap_mapping_range).

   Exporters that shoot down mappings (for any reasons) shall not do any

   synchronization at fault time with outstanding device operations.

   Synchronization is an orthogonal issue to sharing the backing storage of a

   buffer and hence should not be handled by dma-buf itself. This is explictly

   buffer and hence should not be handled by dma-buf itself. This is explicitly

   mentioned here because many people seem to want something like this, but if

   different exporters handle this differently, buffer sharing can fail in

   interesting ways depending upong the exporter (if userspace starts depending

Notifier error injection

========================

Notifier error injection provides the ability to inject artifical errors to

Notifier error injection provides the ability to inject artificial errors to

specified notifier chain callbacks. It is useful to test the error handling of

notifier call chain failures which is rarely executed.  There are kernel

modules that can be used to test the following notifiers.

CPU notifier error injection module

-----------------------------------

This feature can be used to test the error handling of the CPU notifiers by

injecting artifical errors to CPU notifier chain callbacks.

injecting artificial errors to CPU notifier chain callbacks.

If the notifier call chain should be failed with some events notified, write

the error code to debugfs interface