From fc1c73f782263b01037e2247653d4928bc7b3bab Mon Sep 17 00:00:00 2001 From: Mirek Jahoda Date: Mon, 23 Oct 2017 15:25:31 +0000 Subject: [PATCH] Update Java-SecurityManager.xml - title case --- en-US/Java-SecurityManager.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/en-US/Java-SecurityManager.xml b/en-US/Java-SecurityManager.xml index a321573..35fade8 100644 --- a/en-US/Java-SecurityManager.xml +++ b/en-US/Java-SecurityManager.xml @@ -2,7 +2,7 @@
- Interacting with the security manager + Interacting with the Security Manager The Java platform is largely implemented in the Java language itself. Therefore, within the same JVM, code runs which is part @@ -43,7 +43,7 @@
- Security manager compatibility + Security Manager Compatibility A lot of code can run without any additional permissions at all, with little changes. The following guidelines should help to @@ -81,7 +81,7 @@
- Activating the security manager + Activating the Security Manager The usual command to launch a Java application, java, does not activate the security manager. @@ -118,7 +118,7 @@ grant {
- Reducing trust in code + Reducing Trust in Code shows how to run a piece code of with reduced privileges. @@ -176,7 +176,7 @@ grant {
- Re-gaining privileges + Re-gaining Privileges Ordinarily, when trusted code is called from untrusted code, it loses its privileges (because of the untrusted stack frames