Documentation: fix typos found in admin-guide subdirectory

====

CPPC defined in the ACPI spec describes a mechanism for the OS to manage the

performance of a logical processor on a contigious and abstract performance

performance of a logical processor on a contiguous and abstract performance

scale. CPPC exposes a set of registers to describe abstract performance scale,

to request performance levels and to measure per-cpu delivered performance.

* lowest_freq : CPU frequency corresponding to lowest_perf (in MHz).

* nominal_freq : CPU frequency corresponding to nominal_perf (in MHz).

  The above frequencies should only be used to report processor performance in

  freqency instead of abstract scale. These values should not be used for any

  frequency instead of abstract scale. These values should not be used for any

  functional decisions.

* feedback_ctrs : Includes both Reference and delivered performance counter.

Binderfs binder devices can be deleted via `unlink() <unlink_>`_.  This means

that the `rm() <rm_>`_ tool can be used to delete them. Note that the

``binder-control`` device cannot be deleted since this would make the binderfs

instance unuseable.  The ``binder-control`` device will be deleted when the

instance unusable.  The ``binder-control`` device will be deleted when the

binderfs instance is unmounted and all references to it have been dropped.

Finally, you can load high-level drivers for each kind of device that

you have connected.  By default, each driver will autoprobe for a single

device, but you can support up to four similar devices by giving their

individual co-ordinates when you load the driver.

individual coordinates when you load the driver.

For example, if you had two no-name CD-ROM drives both using the

KingByte KBIC-951A adapter, one on port 0x378 and the other on 0x3bc

		/sys/block/zram0/writeback_limit.

	$ echo 1 > /sys/block/zram0/writeback_limit_enable

If admins want to allow further write again once the bugdet is exhausted,

If admins want to allow further write again once the budget is exhausted,

he could do it like below::

	$ echo $((400<<MB_SHIFT>>4K_SHIFT)) > \

- The last developers that touched the source code (if this is done inside

  a git tree). On the above example, Tejun and Bhaktipriya (in this

  specific case, none really envolved on the development of this file);

  specific case, none really involved on the development of this file);

- The driver maintainer (Hans Verkuil);

- The subsystem maintainer (Mauro Carvalho Chehab);

- The driver and/or subsystem mailing list (linux-media@vger.kernel.org);