You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2018/04/18 21:08:14 UTC
[GitHub] ccollins476ad closed pull request #1031: fix/typo
ccollins476ad closed pull request #1031: fix/typo
URL: https://github.com/apache/mynewt-core/pull/1031
This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:
As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/docs/os/core_os/porting/port_os.rst b/docs/os/core_os/porting/port_os.rst
index 406dd41fb..9bafcb8db 100644
--- a/docs/os/core_os/porting/port_os.rst
+++ b/docs/os/core_os/porting/port_os.rst
@@ -71,7 +71,7 @@ the UART to be mapped to several different pins. For these MCUs, the BSP
must specify if and where the UART pins should appear to match the
hardware layout of your system.
-- If your BSP is already supported my Mynewt, there is no additional
+- If your BSP is already supported by Mynewt, there is no additional
BSP work involved in porting to your platform. You need only to set
the ``bsp`` attribute in your Mynewt target using the :doc:`newt command
tool <../../../newt/index>`.
@@ -85,7 +85,7 @@ Some OS code depends on the MCU or SoC that the system contains. For
example, the MCU may specify the potential memory map of the system -
where code and data can reside.
-- If your MCU is already supported my Mynewt, there is no additional
+- If your MCU is already supported by Mynewt, there is no additional
MCU work involved in porting to your platform. You need only to set
the ``arch`` attribute in your Mynewt target using the :doc:`newt command
tool <../../../newt/index>`.
@@ -110,7 +110,7 @@ example, a given CPU core has a specific assembly language instruction
set, and may require special cross compiler or compiler settings to use
the appropriate instruction set.
-- If your CPU architecture is already supported my Mynewt, there is no
+- If your CPU architecture is already supported by Mynewt, there is no
CPU core work involved in porting to your platform. You need only to
set the ``arch`` and ``compiler`` attributes in your Mynewt target
using the :doc:`newt command tool <../../../newt/index>`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services