--- gcc/objc/README	2018/04/24 18:10:14	1.1
+++ gcc/objc/README	2018/04/24 18:20:09	1.1.1.3
@@ -1,11 +1,10 @@
 
-GNU Objective C release notes for gcc 2.4
-*****************************************
+GNU Objective C notes
+*********************
 
-Since gcc 2.3.3 the Objective C as part of gcc has changed a lot.
-This document is to explain what has been done, and a little about
-how specific features differ from other implementations.  The runtime
-has been completely rewritten.  The earlier runtime had several
+This document is to explain what has been done, and a little about how
+specific features differ from other implementations.  The runtime has
+been completely rewritten in gcc 2.4.  The earlier runtime had several
 severe bugs and was rather incomplete.  The compiler has had several
 new features added as well.
 
@@ -62,26 +61,14 @@ This is supported in the style of NeXT T
 headerfile Typedstreams.h for api functions.  I (Kresten) have
 rewritten it in Objective C, but this implementation is not part of
 2.4, it is available from the GNU Objective C prerelease archive. 
-   There is one semathic difference worth noting concerning objects
-stored with objc_write_object_reference (aka NXWriteObjectReference).
-When these are read back in, their object is not guaranteed to be
-available until the `-awake' method is called in the object that
-requests that object.  To objc_read_object you must pass a pointer to
-an id, which is valid after exit from the function calling it (like
-e.g. an instance variable).  In general, you should not use objects
-read in until the -awake method is called.
-
-
-argframe manipulation
-=====================
-
-performv:: will not work properly on all targets.  A primitive
-heuristics is included which tries to determine if and how it should
-be done.  You will get a warning when compiling `objc-msg.c' if the
-euristics doesn't work.
-  Currently there is no notion of the marg_... macros available on the
-NeXT.  That is, the arguments to forward:: can only be used to apply
-the arguments in the stylle of performv::.  We are working on this.
+   There is one difference worth noting concerning objects stored with
+objc_write_object_reference (aka NXWriteObjectReference).  When these
+are read back in, their object is not guaranteed to be available until
+the `-awake' method is called in the object that requests that object.
+To objc_read_object you must pass a pointer to an id, which is valid
+after exit from the function calling it (like e.g. an instance
+variable).  In general, you should not use objects read in until the
+-awake method is called.
 
 
 Acknowledgements
@@ -103,14 +90,6 @@ Steve Naroff <snaroff@next.com> and Rich
 in the compiler.
 
 
-Prerelease Archive
-==================
-
-Intermediate releases, bugfixes and additional other information of
-the GNU Objective C will be available from iesd.auc.dk in the
-directory /pub/ObjC.
-
-
 Bug Reports
 ===========