From 62dabe50d0bb3295d9ea6b1a70717a29c243dd07 Mon Sep 17 00:00:00 2001
From: halw <halw@abb3cda0-5349-4a8f-a601-0c33ac3a8c38>
Date: Sun, 25 Mar 2012 21:39:16 +0000
Subject: [PATCH] Fixed bad links to "Instructions" page.

Author:halw
Date:2012-03-25T21:39:16.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@1055 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
---
 .../et-design-contract-tm-assertions-and-exceptions.wiki      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/current/method/eiffel-tutorial-et/et-design-contract-tm-assertions-and-exceptions.wiki b/documentation/current/method/eiffel-tutorial-et/et-design-contract-tm-assertions-and-exceptions.wiki
index bc603f89..d9edb63f 100644
--- a/documentation/current/method/eiffel-tutorial-et/et-design-contract-tm-assertions-and-exceptions.wiki
+++ b/documentation/current/method/eiffel-tutorial-et/et-design-contract-tm-assertions-and-exceptions.wiki
@@ -38,7 +38,7 @@ In addition to preconditions and postconditions, contract clauses include '''cla
 
 ==Expressing assertions==
 
-Eiffel provides syntax for expressing preconditions (<code>require</code>), postconditions (<code>ensure</code>) and class invariants (<code>invariant</code>), as well as other assertion constructs studied later (see [[ET: Other Mechanisms#Instructions|"Instructions"]] ): loop invariants and variants, check instructions. 
+Eiffel provides syntax for expressing preconditions (<code>require</code>), postconditions (<code>ensure</code>) and class invariants (<code>invariant</code>), as well as other assertion constructs studied later (see "[[ET: Instructions|Instructions]]" ): loop invariants and variants, check instructions. 
 
 Here is a partial update of class <code>ACCOUNT</code> with more assertions: 
 <code>
@@ -135,7 +135,7 @@ Note in this respect that guaranteeing a precondition does not necessarily mean,
 
 possibly with an <code>else</code> part. But if the context of the call, in the client's code, implies that <code>n</code> is positive -- perhaps because some preceding call set it to the sum of two squares -- then there is no need for an <code>if</code> or similar construct. 
 
-{{note|In such a case, a <code>check</code> instruction as introduced later ( [[ET: Other Mechanisms#Instructions|"Instructions"]] ) is recommended if the reason for omitting the test is non-trivial. }}
+{{note|In such a case, a <code>check</code> instruction as introduced later ( "[[ET: Instructions|Instructions]]" ) is recommended if the reason for omitting the test is non-trivial. }}
 
 ==Using contracts for built-in reliability==