[binutils-gdb] Fix examples of the use of the linker script TYPE keyword

[Nick Clifton]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=14848fc2b22e6e718abadcfbcc0491688df19a8e

commit 14848fc2b22e6e718abadcfbcc0491688df19a8e
Author: Nick Clifton <nickc@redhat.com>
Date:   Fri Dec 20 11:00:15 2024 +0000

    Fix examples of the use of the linker script TYPE keyword

Diff:
---
 ld/ld.texi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/ld/ld.texi b/ld/ld.texi
index 6f88b7940a2..f1e06992b50 100644
--- a/ld/ld.texi
+++ b/ld/ld.texi
@@ -5970,19 +5970,19 @@ special requirements of the section type are met.
 Note - the TYPE only is used if some or all of the contents of the
 section do not have an implicit type of their own.  So for example:
 @smallexample
-  .foo . TYPE = SHT_PROGBITS @{ *(.bar) @}
+  .foo . (TYPE = SHT_PROGBITS) : @{ *(.bar) @}
 @end smallexample
 will set the type of section @samp{.foo} to the type of the section
 @samp{.bar} in the input files, which may not be the SHT_PROGBITS
 type.  Whereas:
 @smallexample
-  .foo . TYPE = SHT_PROGBITS @{ BYTE(1) @}
+  .foo . (TYPE = SHT_PROGBITS) : @{ BYTE(1) @}
 @end smallexample
 will set the type of @samp{.foo} to SHT_PROGBBITS.  If it is necessary
 to override the type of incoming sections and force the output section
 type then an extra piece of untyped data will be needed:
 @smallexample
-  .foo . TYPE = SHT_PROGBITS @{ BYTE(1); *(.bar) @}
+  .foo . (TYPE = SHT_PROGBITS) : @{ BYTE(1); *(.bar) @}
 @end smallexample
 
 @item READONLY ( TYPE = @var{type} )