Out of date anaology

Author: Perksey

documentation/proposals/Proposal - Windowing 3.0.md

@@ -75,10 +75,10 @@ those APIs if the user has checked `view is IWindow`. Instead, this proposal bre
 concept of having an abstract "surface" representing a draw area that has been allotted to the application by the
 operating system/window manager, and splits the extant API surface up into distinct "components" that the user can
 access on this "surface". For example, instead of `IWindow.Size = new(1280, 720)`, the user would use
-`ISurface.Bounds.Size = new(1280, 720)` where `Bounds` is an optional component on that surface. Because that component
-is optional, nullable reference types shall be used, which will encourage the user to deal with the scenario in which
-that component is not present as a result of the IDE warnings that would be generated by making an assumption of its
-presence. This provides the write-once-run-everywhere encouragement we're after.
+`Surface.Window.ClientSize = new(1280, 720)` where `Bounds` is an optional component on that surface. Because that
+component is optional, nullable reference types shall be used, which will encourage the user to deal with the scenario
+in which that component is not present as a result of the IDE warnings that would be generated by making an assumption
+of its presence. This provides the write-once-run-everywhere encouragement we're after.
 
 The Working Group may recall that they have already approved a version of this proposal that met some of these goals,
 originally designed by Dylan P and Kai J. Both of us were not fully satisfied with this proposal as this still used the