Documentation contains too many references to Javascript

[patrick-nicodemus]

There are a good number of Javascript references in the documentation for the Python compiler. It is fine to mention it a few times just to indicate that Fable also compiles F# to Javascript, but there are enough mentions that it looks like someone just modified the "F# -> Javascript" documentation and neglected to change a few things.

https://fable.io/Fable.Python/

Easy JavaScript interop
Call Python from Fable or Fable from Python. Use PyPI packages. The entire Python ecosystem is at your fingertips.
Batteries included
Fable supports the F# core library and some common .NET libraries to supplement the JavaScript ecosystem.

https://fable.io/Fable.Python/introduction/py-users-read-this.html

Don’t panic! There is enough documentation to explain how the .NET tools integrate in your environment. And there are basically only two things you need to know:
Fable uses F# project files (.fsproj) to list your F# code files and libraries.
Fable uses NuGet to load F# libraries, which is the equivalent of PyPI for the .NET environment
Voilà. Nothing else. We’ll come to explanations later in the docs. But we promise, there’s nothing you won’t understand right away. Apart from these facts, it’s all JavaScript!

https://fable.io/Fable.Python/communicate/py-from-fable.html

Call Python from Fable
Interoperability is a matter of trust between your statically typed F# code and your untyped dynamic JS code. In order to mitigate risks, Fable gives you several possibilities, amongst them type safety through interface contracts. Sometimes it may sound more convenient to just call JS code in a more dynamic fashion, although be aware by doing this potential bugs will not be discovered until runtime.