Replace GraalVM Enterprise with Oracle GraalVM

Author: LesiaChaban

SECURITY.md

@@ -1,9 +1,6 @@
 # Reporting Security Vulnerabilities
 
-The GraalVM team values the independent security research community and believes
-that responsible disclosure of security vulnerabilities in GraalVM Community
-Edition as well as GraalVM Enterprise Edition helps us ensure the security and
-privacy of all our users.
+The GraalVM team values the independent security research community and believes that responsible disclosure of security vulnerabilities in GraalVM helps us ensure the security and privacy of all our users.
 
 If you believe you have found a security vulnerability, please submit a report
 to [email protected] preferably with a proof of concept. Please refer to
@@ -16,7 +13,7 @@ other channels about a report.
 ### Security Updates, Alerts and Bulletins
 
 GraalVM Community Edition security updates will be released on a quarterly basis
-in conjunction withe GraalVM Enterprise Edition security updates that are part
+in conjunction with the Oracle GraalVM security updates that are part
 of the Oracle Critical Patch Update program. Security updates are released on
 the Tuesday closest to the 17th day of January, April, July and October. A
 pre-release announcement will be published on the Thursday preceding each
@@ -27,7 +24,7 @@ Alerts](https://www.oracle.com/security-alerts/).
 ### Security-Related Information
 
 Please refer to the [GraalVM Security
-Guide](https://www.graalvm.org/security-guide/) for security related topics
+Guide](https://www.graalvm.org/latest/security-guide/) for security related topics
 such as how to support trusted and less trusted code execution using the Truffle
 language framework, or compiler mitigations for transitive execution
 attacks. However please note that we do not currently support the execution of

docs/contributor/CONTRIBUTING.md

@@ -235,9 +235,9 @@ another double-dash:
 Note that there may be a little confusion about the configuration names of
 benchmarks.
 
-##### GraalVM Community and GraalVM Enterprise configurations
+##### GraalVM Community Edition and Oracle GraalVM configurations
 
-We have benchmarks for GraalVM Community and Enterprise. For historical reasons,
+We have benchmarks for GraalVM Community Edition and Oracle GraalVM. For historical reasons,
 these are sometimes referred to in some config files as *CE* and *EE*; *core*
 and *enterprise*; *graalvm_ce* and *graalvm_ee*; or *graalpython_core* and
 *graalpython_enterprise*, respectively.
@@ -252,9 +252,7 @@ via the `--python-vm-config` parameter:
  * `native` - same as `default`, its name is due to the fact that it runs C
    extensions using a mixture of LLVM bitcode interpreted and compiled via
    GraalVM and real native libraries
- * `sandboxed` - this name is historical - this configuration requires a GraalVM
-   Enterprise and runs all C extensions purely as LLVM bitcode on the GraalVM,
-   without any access to the native OS libraries, i.e., using the
+ * `sandboxed` - this name is historical - this configuration requires Oracle  GraalVM and runs all C extensions purely as LLVM bitcode on the GraalVM, without any access to the native OS libraries, i.e., using the
    `--llvm.managed` option for GraalVM.
 
 ##### Configuration of the underlying GraalVM runtime

docs/user/OsInterface.md

@@ -25,7 +25,7 @@ This approach is the most compatible with CPython and provides bare access to th
 By default, this implementation bypasses the Truffle abstraction layer, therefore it is not sandboxed and does not support custom implementations of [Truffle FileSystem service-provider](https://www.graalvm.org/truffle/javadoc/org/graalvm/polyglot/io/FileSystem.html), and other Polyglot API providers related to system interfaces.
 
 The native backend is chosen by default when GraalVM Python is started via the `graalpy` or any other Python related launcher inside GraalVM.
-The exception are Python related launchers with `-managed` suffix available only in GraalVM Enterprise (for example, `graalpy-managed`), which by default use the `java` POSIX backend.
+The exception are Python related launchers with `-managed` suffix available only in Oracle GraalVM (for example, `graalpy-managed`), which by default use the `java` POSIX backend.
 
 ### Limitations of the Native Backend
 
@@ -39,7 +39,7 @@ Known limitations are:
 The `java` backend uses the [Truffle abstraction layer](https://github.com/oracle/graal/blob/master/truffle/docs/README.md) and therefore supports custom Polyglot API providers related to system interfaces and sandboxing.
 Since this abstraction is POSIX agnostic, it does not expose all the necessary functionality. Some functionality is emulated, and some functionality is not supported at all.
 
-The Java backend is the default when GraalVM Python is run via the `Context` API, i.e., [embedded in Java applications](https://github.com/oracle/graal/blob/master/docs/reference-manual/embedding/embed-languages.md), or when it is launched using Python related launchers with `-managed` suffix available only in GraalVM Enterprise.
+The Java backend is the default when GraalVM Python is run via the `Context` API, i.e., [embedded in Java applications](https://github.com/oracle/graal/blob/master/docs/reference-manual/embedding/embed-languages.md), or when it is launched using Python related launchers with `-managed` suffix available only in Oracle GraalVM.
 
 ### Limitations of the Emulated Backend
 

docs/user/ParserDetails.md

@@ -83,7 +83,7 @@ these language options:
 Note that a Python context will not enable writing `.pyc` files by default.
 The `graalpy` launcher enables it by default, but if this is desired in the embedding use case, care should be taken to ensure that the `__pycache__` location is properly managed and the files in that location are secured against manipulation just like the source `.py` files they were derived from.
 
-Note also that to upgrade the application sources to GraalVM Enteprise's Python runtime, old `.pyc`
+Note also that to upgrade the application sources to Oracle GraalVM Python runtime, old `.pyc`
 files must be removed by the embedder as required.
 
 ## Security Considerations