Correct 'to precise' and replace by 'to specify'

src/slides/asciidoc/detailed-design.adoc

@@ -607,11 +607,27 @@ From Smalltalk Best Practices book
 [.impact]
 == GP4: {GP4}
 
+[.columns]
 == Specialization/Generalization Adjustment
 
+[.column.is-two-thirds]
+--
 * Look for reuse: make similar what is almost similar: 
 ** possible changes of operation signatures and attribute types. 
 * Abstract common behaviors and properties. 
+--
+
+[.column]
+--
+[plantuml, align=center]
+....
+class Id << Interface>>
+class GameId
+class PlayerId
+Id <|.. GameId
+Id <|.. PlayerId
+....
+--
 
 [.notes]
 --
@@ -620,21 +636,36 @@ possible changes to the signature of operations
 Abstraction of common behaviors, libraries
 --
 
+[.columns]
 == Attributes
 
-.Precise: 
+[.column.is-two-third]
+--
+.Specify: 
 * Default values 
 * Multiplicities: [0..1], [*], etc. 
 * Constraints (OCL expressions). 
 * Modifiers: readOnly, redefines, etc. 
 * Visibility. 
-* Use OCL to precise derived attribute. 
- wir
+* Use OCL to specify derived attribute. 
+--
+
+[.column]
+--
+[plantuml, align=center]
+....
+class Player {
+    + id  : Integer {id}
+    + age : Integer {readOnly}
+}
+....
+--
+
 
 == Association Roles
 
-* Precise the relationships between different roles: union, subsets <x>, redefines <y>, ordered, unique, etc. 
-* Precise navigability. 
+* Specify the relationships between different roles: union, subsets <x>, redefines <y>, ordered, unique, etc. 
+* Specify navigability. 
 
 [.notes]
 --
@@ -646,9 +677,8 @@ Les associations unidirectionnelles sont plus simples à implémenter.
 
 * Use OCL expressions to specify pre- and post-conditions. 
 * Use the Action Semantics (xUML) to specify operation body. 
-* Precise parameters directions (in, out, in/out). 
-* Precise return parameter properties: readOnly, ordered, etc. 
-
+* Specify parameters directions (`in`, `out`, `in/out`). 
+* Specify return parameter properties: `readOnly`, `ordered`, etc. 
 
 
 [.impact]