From: Arnaud Charlet <charlet@gcc.gnu.org>
Date: Thu, 23 Jan 2014 16:56:32 +0000 (+0100)
Subject: Minor editing.
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=7e97e1742acd7bd89f44af38315ec93004b90207;p=gcc.git

Minor editing.

From-SVN: r206989
---

diff --git a/gcc/ada/gnat_rm.texi b/gcc/ada/gnat_rm.texi
index adf4ec20a9d..a4b47d95299 100644
--- a/gcc/ada/gnat_rm.texi
+++ b/gcc/ada/gnat_rm.texi
@@ -4249,14 +4249,15 @@ pragma Linker_Section (
 @end smallexample
 
 @noindent
-@var{LOCAL_NAME} must refer to an object that is declared at the library
-level. This pragma specifies the name of the linker section for the given
-entity. It is equivalent to @code{__attribute__((section))} in GNU C and
-causes @var{LOCAL_NAME} to be placed in the @var{static_string_EXPRESSION}
-section of the executable (assuming the linker doesn't rename the section).
-
-The compiler normally places library-level objects in standard sections
-depending on their type: procedures and functions generally go in the
+@var{LOCAL_NAME} must refer to an object or a subprogram that is
+declared at the library level. This pragma specifies the name of the
+linker section for the given entity. It is equivalent to
+@code{__attribute__((section))} in GNU C and causes @var{LOCAL_NAME} to
+be placed in the @var{static_string_EXPRESSION} section of the
+executable (assuming the linker doesn't rename the section).
+
+The compiler normally places library-level entities in standard sections
+depending on the class: procedures and functions generally go in the
 @code{.text} section, initialized variables in the @code{.data} section
 and uninitialized variables in the @code{.bss} section.