diff --git a/documentation/trunk/eiffel/Language_reference/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki b/documentation/trunk/eiffel/Language_reference/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
index 2616d26e..f754eaf0 100644
--- a/documentation/trunk/eiffel/Language_reference/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
+++ b/documentation/trunk/eiffel/Language_reference/void-safe-programming-eiffel/converting-existing-software-void-safety/index.wiki
@@ -76,7 +76,7 @@ So, fix any problems that arise out of turning on full class checking.
 
 The second step in conversion of existing software is to change the values of the other void-safe related project settings and use the void-safe configurations for any delivered libraries and precompilations.
 
-In the project settings for the target in which you are working, set '''Void-safe''' to either '''Complete''', '''Initialization''' or '''Conformance'''. 
+In the project settings for the target in which you are working, set '''Void safety''' to '''Complete''', '''Transitional''' , '''Initialization''' or '''Conformance'''. 
 
 {{note|Remember that during a transitional period starting with v6.4, there will be multiple versions of the configuration files for Eiffel libraries and precompiles. For example, base.ecf (void-unsafe) and base-safe.ecf (void-safe). Starting with v16.11 there is only one configuration file for libraries (e.g., base.ecf) that works with both void-safe and void-unsafe client software, but if you are using a precompile, there could be different versions for void-safe and void-unsafe precompiles.}}