markup modification: distinguish blocks and groups

1 files changed, 4 insertions, 4 deletions

diff --git a/data/samples/current/en/gpl3.fsf.sst b/data/samples/current/en/gpl3.fsf.sst
index 3c055e7..747eda4 100644
--- a/data/samples/current/en/gpl3.fsf.sst
+++ b/data/samples/current/en/gpl3.fsf.sst
@@ -253,7 +253,7 @@ If you develop a new program, and you want it to be of the greatest possible use
 
 To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
 
-poem{
+block{
 
     <one line to give the program's name and a brief idea of what it does.>
     Copyright (C) <year> <name of author>
@@ -271,20 +271,20 @@ poem{
     You should have received a copy of the GNU General Public License
     along with this program. If not, see http://www.gnu.org/licenses/.
 
-}poem
+}block
 
 Also add information on how to contact you by electronic and paper mail.
 
 If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:
 
-poem{
+block{
 
     <program> Copyright (C) <year> <name of author>
     This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
     This is free software, and you are welcome to redistribute it
     under certain conditions; type 'show c' for details.
 
-}poem
+}block
 
 The hypothetical commands 'show w' and 'show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box".