diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki
index cddd8e84..73b16db9 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/using-autotest/using-generated-tests.wiki
@@ -12,7 +12,7 @@ The first bit of knowledge comes from the ''preconditions'' of target routines.
 
 You may look at a synthesized test class and think that it seems to be very long and to contain lots of stuff that you doubt is relevant. This is a fair assessment. The processes that the Eiffel Testing Framework uses to build synthesized tests are constantly being improved. But for now, synthesized tests, although useful, are not always things of extraordinary beauty. 
 
-So for the time being, unlike manual and extracted tests, you should not make synthesized tests a part of your permanent test suite. Rather, you should consider them a disposable means to an end. Use each synthesized tests as a guide for building an effective and readable manual test. 
+So for the time being, unlike manual and extracted tests, you should not make synthesized tests a part of your permanent test suite. Rather, you should consider them a disposable means to an end. Use each synthesized test as a guide for building an effective and readable manual test. 
 
 
 ==Creating synthesized tests==
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/eiffelstudio-6-release-notes/release-notes-eiffelstudio-64.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/eiffelstudio-6-release-notes/release-notes-eiffelstudio-64.wiki
index b543b044..bac6550d 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/eiffelstudio-6-release-notes/release-notes-eiffelstudio-64.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/eiffelstudio-release-notes/eiffelstudio-6-release-notes/release-notes-eiffelstudio-64.wiki
@@ -6,7 +6,7 @@
 
 ===What's new===
 * Initial support for the iPhone platform to develop command line applications. Support for graphical applications will be available in the next release.
-* Added new libraries: the '''api wrapper''', '''diff''', the '''encoding''', and '''internationalization''' libraries.
+* Added new libraries: '''api wrapper''', '''diff''', '''encoding''', and '''internationalization''' libraries.
 * To minimize breaking changes, EiffelStudio comes with two sets of libraries. The first set, which is the default set, is compatible with previous versions of EiffelStudio. The second set, which is labeled '''experimental''', is void-safe and contains some breaking changes such as new ARRAY, ARRAYED_LIST, HASH_TABLE, SPECIAL classes. Users are encouraged to compile with the experimental libraries in order to prepare their code for the future when today's experimental libraries will become the de facto libraries. It is possible to adjust code so that a single version compiles against both sets of libraries.
 * Added new tools to the EiffelStudio delivery. They are located under $ISE_EIFFEL/tools/spec/$ISE_PLATFORM/bin. The new tools are:
 :*'''compile_all''': compile all the Eiffel Configuration File projects found under a directory and report which ones do and do not compile.
@@ -45,6 +45,8 @@
 ==Libraries==
 
 ===EiffelBase===
+* Changed the default assigner of <eiffel>{TABLE}.item</eiffel> from originally <eiffel>put</eiffel> to <eiffel>force</eiffel>. As a consequence, descendants of <eiffel>TABLE</eiffel> might get a VDRD error if redefining <eiffel>item</eiffel>
+* Added <eiffel>same_keys</eiffel> to <eiffel>HASH_TABLE</eiffel>. You can redefine this feature to use a different comparison criterion for the keys. 
 * For object comparison, containers are now using the ~ operator instead of  <eiffel>is_equal</eiffel>. As a result, if you had heterogeneous containers, then it might not find items that were found before (although it was a catcall). 
 * EiffelBase is now using the <eiffel>alias</eiffel> notation instead of <eiffel>infix/prefix</eiffel>.
 * Updated the IMMUTABLE_STRING classes to have an efficient string extraction query <eiffel>shared_substring</eiffel> which will let you create a substring of an existing immutable string without actually duplicating the data.
@@ -66,7 +68,6 @@
 * Fixed eweasel test#array005 where calling <eiffel>wipe_out</eiffel> on an <eiffel>ARRAY2</eiffel> was violating the invariant. 
 * Fixed eweasel test#except035 where we incorrectly merged the code value for <eiffel>IO_EXCEPTION</eiffel> and <eiffel>RUNTIME_IO_EXCEPTION</eiffel> thus breaking existing code not based on Eiffel exception object.
 * Fixed eweasel test#except033 that an exception thrown through rescues caused infinite loop. 
-* Added <eiffel>same_keys</eiffel> to <eiffel>HASH_TABLE</eiffel>. You can redefine this feature to use a different comparison criterion for the keys. 
 
 ===EiffelNet===
 * Added ability to only listen on the loopback address in <eiffel>NETWORK_STREAM_SOCKET</eiffel>.