doc V3.3.3

saspy/doc/source/install.rst

@@ -433,6 +433,8 @@ on any supported platform.
 
 
 ATTN, as of saspy version 3.3.3, the classpath is no longer required!
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 The 4 required IOM Java client jars are now included in the saspy repo, and they, along with the saspyiom.jar and the 
 thirdparty CORBA jars will be automatically provided as the calsspath by saspy. This is generally all that is needed.
 If you require the 3 encryption jars, shown below, they still need to be acquired from your SAS deployment, and then
@@ -558,8 +560,7 @@ iomhost -
 iomport - 
     (Required) The port that object spawner is listening on for workspace server connections (workspace server port - not object spawner port!).
 classpath - 
-    (Mo longer Required) Unless you require the 3 encryption jars, you no longer need to specify this. If you do have to use those 3 jars,
-    then provide the complete classpath with all of the jars in it like previously required.
+    (No longer Required) As of V3.3.3 this is no longer required. See instuctions above (ATTN, as of saspy version 3.3.3, the classpath is no longer required!) 
 authkey -
     The keyword that starts a line in the authinfo file containing user and or password for this connection.
 omruser - 
@@ -700,7 +701,7 @@ github site: https://github.com/sassoftware/saspy-examples/blob/master/SAS_contr
 java      - 
     (Required) The path to the Java executable to use. 
 classpath - 
-    (Mo longer Required) This is now generated by saspy and not nexessary for Local mode at all. 
+    (No longer Required) As of V3.3.3 this is no longer required.
 encoding  -
     NOTE: as of saspy V2.4.2, you no longer need to set the encoding. SASpy
     will determine the SAS session encoding and map that to the Python encoding for you.