Update multilang.md

docs/src/concepts/multilang.md

@@ -2,40 +2,25 @@
 
 The Caesar framework is not limited to direct Julia use. 
 
+## NavAbility SDKs and APIs
+
+The maintainers of Caesar.jl together with NavAbility.io are developing a standardized SDK / API for much easier multi-language / multi-access use of the solver features.  The [Documentation for the NavAbilitySDK's can be found here](https://navability.github.io/NavAbilitySDK.py/).
+
+Contact [email protected] for more information.
+
 ## Static, Shared Object `.so` Compilation
+
 See [Compiling Binaries](@ref compile_binaries).
 
 ## ROS Integration
+
 See [ROS Integration](@ref ros_direct).
 
 ## Python Direct
 
 For completeness, another design pattern is to wrap Julia packages for direct access from python, see [SciML/diffeqpy](https://github.com/SciML/diffeqpy) as example.
 
-## Caesar SDKs and APIs
-
-The maintainers of Caesar.jl together with NavAbility.io are developing a standardized SDK / API for much easier multi-language / multi-access use of the solver features.  Contact [email protected] for more information.
-
-!!! note
-    2021Q4, Coming Soon!  A new multilanguage SDK is under development and will replace and consolidate the previous methods listed below.
-
-### Previous Generation APIs
-
-The following Github projects provide access to features of Caesar in their language:
-
-* Julia Web interface:
-  * [GraffSDK.jl](https://github.com/GearsAD/GraffSDK.jl)
-
-* ZMQ Interface
-  * C/C++:
-    * [Graff Cpp](https://github.com/MarineRoboticsGroup/graff_cpp)
-    * [Caesar LCM](http://github.com/pvazteixeira/caesar-lcm)
-    * [Caesar ROS](http://github.com/pvazteixeira/caesar_ros)
-  * Python:
-    * [GraffSDK.py](https://github.com/nicrip/graff_py) (needs to be updated)
-    * [Synchrony_py](https://github.com/nicrip/SynchronySDK_py)
-
-## ZMQ Messaging Interface
+## [OUTDATED] ZMQ Messaging Interface
 
 Caesar.jl has a ZMQ messaging interface ([interested can see code here](https://github.com/JuliaRobotics/Caesar.jl/blob/master/src/zmq/ZmqCaesar.jl)) that allows users to interact with the solver code base in a variety of ways.  The messaging interface is not meant to replace static `.so` library file compilation but rather provide a more versatile and flexible development strategy.