update README

README

@@ -78,14 +78,14 @@ file" given from the command line. Graphene provides three options for
 spcifying the programs and manifest files:
 
     option 1: (automatic manifest)
-    [PATH_TO_PAL]/libpal.so [PROGRAM] [ARGUMENTS]...
+    [PATH TO Pal/src]/pal [PROGRAM] [ARGUMENTS]...
     (Manifest file: "[PROGRAM].manifest" or "manifest")
 
     option 2: (given manifest)
-    [PATH_TO_PAL]/libpal.so [MANIFEST] [ARGUMENTS]...
+    [PATH TO Pal/src]/pal [MANIFEST] [ARGUMENTS]...
 
     option 3: (manifest as a script)
-    [PATH_TO_MANIFEST]/[MANIFEST] [ARGUMENTS]...
+    [PATH TO MANIFEST]/[MANIFEST] [ARGUMENTS]...
     (Manifest must have "#![PATH_TO_PAL]/libpal.so" as the first line)
 
 Using "libpal.so" as loader to start Graphene will not attach the applications
@@ -96,16 +96,15 @@ reference monitor loader (libpal_sec.so). Graphene provides three options for
 spcifying the programs and manifest files to the loader:
 
     option 4: (automatic manifest - with reference monitor)
-    [PATH_TO_PAL]/libpal.so [PROGRAM] [ARGUMENTS]...
+    [PATH TO Pal/src]/pal_sec [PROGRAM] [ARGUMENTS]...
     (Manifest file: "[PROGRAM].manifest" or "manifest")
 
     option 5: (given manifest - with reference monitor)
-    [PATH_TO_PAL]/libpal.so [MANIFEST] [ARGUMENTS]...
+    [PATH TO Pal/src]/pal_sec [MANIFEST] [ARGUMENTS]...
 
     option 6: (manifest as a script - with reference monitor)
-    [PATH_TO_MANIFEST]/[MANIFEST] [ARGUMENTS]...
-    (Manifest must have "#![PATH_TO_PAL]/libpal.so" as the first line)
-
+    [PATH TO MANIFEST]/[MANIFEST] [ARGUMENTS]...
+    (Manifest must have "#![PATH TO Pal/src]/pal_sec" as the first line)
 
 Although manifest files are optional for Graphene, running an application
 usually requires some minimal configuration in its manifest file. A