OvmfPkg/Xen: Fix various typos

Fix various typos in comments and documentation.

Cc: Jordan Justen <jordan.l.justen@intel.com>
Cc: Laszlo Ersek <lersek@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Anthony Perard <anthony.perard@citrix.com>
Cc: Julien Grall <julien@xen.org>
Signed-off-by: Antoine Coeur <coeur@gmx.fr>
Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>
Acked-by: Anthony PERARD <anthony.perard@citrix.com>
Acked-by: Laszlo Ersek <lersek@redhat.com>
Signed-off-by: Philippe Mathieu-Daude <philmd@redhat.com>
Message-Id: <20200207010831.9046-61-philmd@redhat.com>

OvmfPkg/Include/Protocol/XenBus.h

@@ -215,7 +215,7 @@ XENSTORE_STATUS
   Grant access to the page Frame to the domain DomainId.
 
   @param This       A pointer to XENBUS_PROTOCOL instance.
-  @param DomainId   ID of the domain to grant acces to.
+  @param DomainId   ID of the domain to grant access to.
   @param Frame      Frame Number of the page to grant access to.
   @param ReadOnly   Provide read-only or read-write access.
   @param RefPtr     Reference number of the grant will be written to this pointer.
@@ -266,7 +266,7 @@ UINT32
   Send an event to the remote end of the channel whose local endpoint is Port.
 
   @param This       A pointer to the XENBUS_PROTOCOL.
-  @param Port       Local port to the the event from.
+  @param Port       Local port to the event from.
 
   @retval UINT32    The return value from the hypercall, 0 if success.
 **/

OvmfPkg/Include/Protocol/XenIo.h

@@ -1,7 +1,7 @@
 /** @file
   XenIo protocol to abstract arch specific details
 
-  The Xen implementations for the Intel and ARM archictures differ in the way
+  The Xen implementations for the Intel and ARM architectures differ in the way
   the base address of the grant table is communicated to the guest. The former
   uses a virtual PCI device, while the latter uses a device tree node.
   In order to allow the XenBusDxe UEFI driver to be reused for the non-PCI