diff --git a/documentation/22.12/eiffel/Language_reference/void-safe-programming-eiffel/index.wiki b/documentation/22.12/eiffel/Language_reference/void-safe-programming-eiffel/index.wiki
index d819899f..683eb72a 100644
--- a/documentation/22.12/eiffel/Language_reference/void-safe-programming-eiffel/index.wiki
+++ b/documentation/22.12/eiffel/Language_reference/void-safe-programming-eiffel/index.wiki
@@ -1,3 +1,5 @@
+[[Property:modification_date|Mon, 23 Jan 2023 09:20:10 GMT]]
+[[Property:publication_date|Mon, 23 Jan 2023 09:20:10 GMT]]
 [[Property:link_title|Void-safe programming]]
 [[Property:title|Void-safe programming in Eiffel]]
 [[Property:weight|10]]
@@ -6,7 +8,7 @@
 
 When you develop software in Eiffel, you can be assured (at compile time) that your system will not attempt (at run time) to apply a feature to a void reference -- or, in the terminology of other languages such as C, "dereference a null pointer".
 
-Throughout the history of Eiffel, new capabilities -- agents, the SCOOP concurrency mechanism and many others -- have added considerable expressive power to the languag,e while causing minimum impact on existing software. Void-safe Eiffel is such an innovation, which instead of adding new mechanisms ''removes'' a major source of instability in programs, present in all other major languages: null-pointer dereferencing. To say that Eiffel is void-safe means that such catastrophic yet common errors simply will not occur.
+Throughout the history of Eiffel, new capabilities -- agents, the SCOOP concurrency mechanism and many others -- have added considerable expressive power to the language while causing minimum impact on existing software. Void-safe Eiffel is such an innovation, which instead of adding new mechanisms ''removes'' a major source of instability in programs, present in all other major languages: null-pointer dereferencing. To say that Eiffel is void-safe means that such catastrophic yet common errors simply will not occur.
 
 There is in fact no need to speak of "void-safe Eiffel". The language is just Eiffel... and it is void-safe, just as it is statically typed.  We still occasionally refer to "Void-safe Eiffel" simply because until 2005 or so Eiffel was not void-safe (it had to start somewhere), and you may still encounter older documentation that talks about "calls on void targets" (null-pointer dereferences). But in today's Eiffel such an event is impossible.