Merge pull request #74 from pathakraul/rpathak_arcdraft

Fix typos in all chapters

src/message-protocol.adoc

@@ -192,7 +192,7 @@ the <<Possible Error Codes>>. An RPMI service where the response data exceeds
 the maximum message data size can use multipart RPMI acknowledgement messages.
 
 === Notifications
-The platform microcrontroller can use RPMI notification message to notify
+The platform microcontroller can use RPMI notification message to notify
 application processors about system events which are also referred to as
 *RPMI events*. An RPMI notification message has no associated response or
 acknowledgement from application processors. Multiple RPMI events can be

src/rpmi-mpxy.adoc

@@ -14,10 +14,10 @@ A platform with limited number of RPMI transport instances can share an M-mode
 RPMI transport instance with the supervisor software using the SBI MPXY extension
 cite:[SBI]. An M-mode firmware or hypervisor can also virtualize RPMI message
 communication for the supervisor software using the SBI MPXY extension. As shown
-in the <<mpyx_rpmi_integration>> below, the SBI implementation acts as a *RPMI proxy*
+in the <<mpxy_rpmi_integration>> below, the SBI implementation acts as a *RPMI proxy*
 for the supervisor software when sending RPMI messages through an SBI MPXY channel.
 
-[#mpyx_rpmi_integration]
+[#mpxy_rpmi_integration]
 .RPMI and SBI MPXY Integration
 image::mpxy-rpmi.png[350,350, align="center"]
 

src/srvgrp-management.adoc

@@ -179,7 +179,7 @@ The `MM_COMMUNICATE` service invokes an MM service implemented in the secure
 execution environment. The input data needed to identify and invoke the MM
 service is referred to as `MM_COMM_INPUT_DATA` whereas the output data returned
 by the MM service is referred to as `MM_COMM_OUTPUT_DATA`. The RPMI client in
-the non-secure execution enviroment provides the location of `MM_COMM_INPUT_DATA`
+the non-secure execution environment provides the location of `MM_COMM_INPUT_DATA`
 and `MM_COMM_OUTPUT_DATA` in the MM shared memory as parameters of `MM_COMMUNICATE`
 service.
 

src/srvgrp-request-forward.adoc

@@ -127,7 +127,7 @@ This service allows application processors to retrieve the current forwarded RPM
 request message. The current message may be the oldest forwarded RPMI request
 message in the platform microcontroller (or SBI implementation) queue.
 
-[#table_reqfwd_retireve_current_message_request_data]
+[#table_reqfwd_retrieve_current_message_request_data]
 .Request Data
 [cols="1, 3, 1, 7", width=100%, align="center", options="header"]
 |===
@@ -144,7 +144,7 @@ message in the platform microcontroller (or SBI implementation) queue.
 bytes.
 |===
 
-[#table_reqfwd_retireve_current_message_response_data]
+[#table_reqfwd_retrieve_current_message_response_data]
 .Response Data
 [cols="1, 3, 1, 7a", width=100%, align="center", options="header"]
 |===

src/srvgrp-system-suspend.adoc

@@ -126,7 +126,7 @@ if a `SUSPEND_TYPE` supports resume address.
 | Suspend type. See <<section-suspend-types>> for more details.
 |===
 
-[#table_syssuspend_getsysuspendattrs_response_data]
+[#table_syssuspend_getsyssuspendattrs_response_data]
 .Response Data
 [cols="1, 2, 1, 7a", width=100%, align="center", options="header"]
 |===

src/srvgrp-voltage.adoc

@@ -332,7 +332,7 @@ Refer to <<voltage-level-format-section>> for more details.
 ----
 !===
 | 2
-|NUM_LEVELS
+| NUM_LEVELS
 | uint32
 | Number of voltage levels (number of arrays)
 supported by the domain. Get the voltage levels with `VOLT_GET_SUPPORTED_LEVELS`.

src/transport.adoc

@@ -116,8 +116,8 @@ image::highlevel-arch-queues.png[align="center"]
 ==== Queue Types
 The RPMI shared memory transport consists of four unidirectional queues. The
 type of messages and the direction of message delivery is fixed for each RPMI
-shared memory trasport queue. The <<transport_shared_memory_queues>> below
-provides a more detailed description of all RPMI shared memory tranpsort queues.
+shared memory transport queue. The <<transport_shared_memory_queues>> below
+provides a more detailed description of all RPMI shared memory transport queues.
 
 [#transport_shared_memory_queues]
 .Shared Memory Transport Queues
@@ -162,7 +162,7 @@ image::highlevel-flow.png[400,400, align="center"]
 An RPMI shared memory queue is divided into `M` contiguous slots of equal size
 which are used to form a circular queue. The size of each slot (or slot size)
 must be a `power-of-2` and must be at least `64 bytes`. The slot size is same
-accross all RPMI shared memory queues and the physical address of each slot
+across all RPMI shared memory queues and the physical address of each slot
 must be aligned at slot size boundary.
 
 NOTE: The slot size should match with the maximum cache line size used in a
@@ -184,7 +184,7 @@ view of the RPMI shared memory queue internals is shown in the
 
 NOTE: The requirement of keeping `head` and `tail` in separate slots is
 to prevent both `head` and `tail` using the same cache line so that cache
-maintainence can be done separately for both `head` and `tail`.
+maintenance can be done separately for both `head` and `tail`.
 
 [#transport_shared_memory_qint]
 .Shared Memory Queue Internals