Reduced use of :abbr:

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/source/appendix-a.rst b/doc/source/appendix-a.rst
index 3d456c2..b38018c 100644
--- a/doc/source/appendix-a.rst
+++ b/doc/source/appendix-a.rst
@@ -3,7 +3,7 @@ Appendix A: custom eCos configuration
 
 ECos is called a *configurable* system for a reason: it contains a powerful infrastructure for choosing what system components and abstractions are included and how they are configured.
 
-This Appendix will describe briefly how to deal with :abbr:`.ecc` files for the Colibri VF61.
+This Appendix will describe briefly how to deal with ``.ecc`` files for the Colibri VF61.
 
 Background
 ----------
@@ -30,7 +30,7 @@ Templates
 
 :program:`configtool` allows the user to build the system however they want using a graphical user interface, provided constraints in :file:`.cdl` files describing the system structure are maintained.
 
-While creating a new :abbr:`.ecc` file it is easier to also use a predefined template representing common use scenarios, such as **posix** which represents a system which has all the necessary packages to run typical POSIX programs or **redboot** which understandably is used to build a binary of RedBoot, the eCos bootloader.
+While creating a new ``.ecc`` file it is easier to also use a predefined template representing common use scenarios, such as **posix** which represents a system which has all the necessary packages to run typical POSIX programs or **redboot** which understandably is used to build a binary of RedBoot, the eCos bootloader.
 
 In order to select a template to base upon, use :menuselection:`build --> templates`.
 
@@ -38,7 +38,7 @@ In order to select a template to base upon, use :menuselection:`build --> templa
 
    Remember that the templates are just general scenarios, which may contain settings incompatible with the desired ones (baudrates, console mangling, debug console choice, presence of RedBoot ROM monitor). It is necessary to tweak them according to your needs.
 
-Preparing an :abbr:`.ecc` file using :program:`configtool`
+Preparing an ``.ecc`` file using :program:`configtool`
 ----------------------------------------------------------
 
 Launch :program:`configtool`. 
@@ -47,7 +47,7 @@ Select :menuselection:`build --> repository` specify the path to eCos repository
 Select the :menuselection:`build --> template` option and choose the :guilabel:`Toradex Colibri VF61` as your hardware platform with default set of packages.
 Click :guilabel:`continue` to proceed.
 
-When the default set of packages is used for the platform, the associated :abbr:`.ecc` file can already be prepared.
+When the default set of packages is used for the platform, the associated ``.ecc`` file can already be prepared.
 Save it in a directory accessible by your build script and **remember to point to it in** :ref:`the kernel build script <build-kernel>`.
 
 Other packages can be added from :menuselection:`build --> packages`, bear in mind that you may need to alter the chosen packages and options to satisfy some ``.cdl`` constraints.
@@ -58,7 +58,7 @@ Startup memory choice
 ---------------------
 
 There are three memories from which eCos software may be launched in Colibri VF61.
-This is determined in the :abbr:`.ecc` file the eCos kernel was based on.
+This is determined in the ``.ecc`` file the eCos kernel was based on.
 
 By default the software is prepared to be launched from OnChip RAM (OCRAM).
 Alternatively DRAM memory may be used for booting.