[PATCH 4/4] eng: Clarify "Coding Conventions" introduction

[Gedare Bloom]

all 4 look good to me.

On Thu, Nov 5, 2020 at 11:43 AM Sebastian Huber
<sebastian.huber at embedded-brains.de> wrote:
>
> ---
>  eng/coding-conventions.rst | 10 +++++-----
>  1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/eng/coding-conventions.rst b/eng/coding-conventions.rst
> index 5dd8df5..e34cd74 100644
> --- a/eng/coding-conventions.rst
> +++ b/eng/coding-conventions.rst
> @@ -9,11 +9,11 @@
>  Coding Conventions
>  ******************
>
> -The style of RTEMS is generally consistent in the core areas.
> -This page attempts to capture generally accepted practices.
> -When in doubt, consult the code around you or look in cpukit/rtems.
> -See the sister page `Doxygen Recommendations <https://devel.rtems.org/wiki/Developer/Coding/Doxygen>`_.
> -for examples that illustrate style rules and Doxygen usage.
> +The style of RTEMS is generally consistent in the core areas.  This section
> +attempts to capture generally accepted practices.  When in doubt, consult the
> +code around you, look in the RTEMS sources in the directories
> +:file:`cpukit/include/rtems/score` and :file:`cpukit/score`, or ask on the
> +:r:list:`devel`.
>
>  Source Documentation
>  --------------------
> --
> 2.26.2
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel