Build 1.0.80

etc/build/config.props

@@ -11,7 +11,7 @@
 //
 
 // default version used by build scripts
-buildVersion=1.0.79
+buildVersion=1.0.80
 
 // Must be configured boot build in substitute/release installation
 //devHome=/work/fan/
@@ -24,4 +24,5 @@ buildVersion=1.0.79
 // dotnetHome=/C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/
 
 // Mac setup
-//jdkHome=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/
+//jdkHome=/System/Library/Frameworks/JavaVM.framework/Versions/CurrentJDK/Home/
+

src/doc/docIntro/doc/ChangeLog.fandoc

@@ -6,7 +6,7 @@
 ** license:    Licensed under the Academic Free License version 3.0
 **************************************************************************
 
-*Build 1.0.80 (working)*
+*Build 1.0.80 (23 Apr 2024)*
 - New ECMA class-based JavaScript design
 - Move fwt pods into separate repo
 - Crypto JWT and JWK APIs

src/doc/docLang/doc/Actors.fandoc

@@ -96,7 +96,7 @@ Futures [#futures]
 ******************
 All three send methods return a [Future]`concurrent::Future` which may
 used to access the result of that message.  You can poll for the
-result using `concurrent::Future.state` - a future enters the complete
+result using `concurrent::Future.status` - a future enters the complete
 state by one of three transitions:
   - The actor processes the message and returns a result
   - The actor raises an exception while processing the message
@@ -270,4 +270,5 @@ shutdown.  Unlike 'stop', kill doesn't give actors a chance to finish
 processing their pending message queues - all pending messages are cancelled.
 Actors which are currently  executing a message are interrupted (which may
 or may not immediately terminate that thread).  Once all actors have
-relinquished their threads, the ActorPool enters the *done* state.
+relinquished their threads, the ActorPool enters the *done* state.
+