Minor update on Jobs API docs (#200)

Author: qiuosier

docs/source/user_guide/jobs/data_science_job.rst

@@ -8,6 +8,7 @@ Quick Start
 
   See :doc:`policies` and  `About Data Science Policies <https://docs.oracle.com/en-us/iaas/data-science/using/policies.htm>`_.
 
+
 Define a Job
 ============
 

docs/source/user_guide/jobs/infra_and_runtime.rst

@@ -3,7 +3,6 @@ Infrastructure and Runtime
 
 This page describes the configurations of **Infrastructure** and **Runtime** defining a Data Science Job.
 
-.. include:: ../jobs/toc_local.rst
 
 Example
 =======
@@ -99,9 +98,42 @@ a service gateway, both are configured automatically. Custom networking requires
 You can control the network access through the subnet and security lists.
 
 If you specified a subnet ID, your job will be configured to have custom networking.
-Otherwise, default networking will be used. Note that when you are in a Data Science Notebook Session,
+Otherwise, default networking will be used.
+
+Note that when you are in a Data Science Notebook Session,
 the same networking configuration is be used by default.
 You can specify the networking manually by calling :py:meth:`~ads.jobs.DataScienceJob.with_job_infrastructure_type()`.
+For example, if you are using custom networking in the notebook session
+but you would like to use default networking for the job:
+
+.. tabs::
+
+  .. code-tab:: python
+    :caption: Python
+
+    from ads.jobs import DataScienceJob
+
+    infrastructure = (
+        DataScienceJob()
+        .with_log_group_id("<log_group_ocid>")
+        .with_log_id("<log_ocid>")
+        # Use default networking,
+        # regardless of the networking used by the notebook session
+        .with_job_infrastructure_type("ME_STANDALONE")
+        # compartment ID, project ID, compute shape and block storage will be
+        # the same as the ones set in the notebook session
+    )
+
+  .. code-tab:: yaml
+    :caption: YAML
+
+    kind: infrastructure
+    type: dataScienceJob
+    spec:
+      jobInfrastructureType: ME_STANDALONE
+      logGroupId: <log_group_ocid>
+      logId: <log_ocid>
+
 
 Logging
 -------

docs/source/user_guide/jobs/policies.rst

@@ -15,7 +15,7 @@ This section describe the policies you might need for running Data Science Jobs.
 
     In the following example, ``group <your_data_science_users>`` is the subject of the policy
     when using OCI API keys for authentication. For resource principal authentication,
-    the subject should be a ``dynamic-group``, for example, ``dynamic-group <your_resources>``
+    the subject should be a ``dynamic-group``, for example, ``dynamic-group <your_dynamic_group>``
 
 Here is an example defining a dynamic group for all job runs in a compartment:
 
@@ -38,19 +38,19 @@ The following policies are for job runs to access other OCI resources:
 
 .. code-block::
 
-    Allow dynamic-group <your_resources> to read repos in compartment <your_compartment_name>
-    Allow dynamic-group <your_resources> to use data-science-family in compartment <your_compartment_name>
-    Allow dynamic-group <your_resources> to use virtual-network-family in compartment <your_compartment_name>
-    Allow dynamic-group <your_resources> to use log-groups in compartment <your_compartment_name>
-    Allow dynamic-group <your_resources> to use logging-family in compartment <your_compartment_name>
-    Allow dynamic-group <your_resources> to manage objects in compartment <your_compartment_name> where all {target.bucket.name=<your_bucket_name>}
-    Allow dynamic-group <your_resources> to use buckets in compartment <your_compartment_name> where all {target.bucket.name=<your_bucket_name>}
+    Allow dynamic-group <your_dynamic_group> to read repos in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to use data-science-family in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to use virtual-network-family in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to use log-groups in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to use logging-family in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to manage objects in compartment <your_compartment_name> where all {target.bucket.name=<your_bucket_name>}
+    Allow dynamic-group <your_dynamic_group> to use buckets in compartment <your_compartment_name> where all {target.bucket.name=<your_bucket_name>}
 
 The following policy is needed for running a container job:
 
 .. code-block::
 
-    Allow dynamic-group <your_resources> to read repos in compartment <your_compartment_name>
+    Allow dynamic-group <your_dynamic_group> to read repos in compartment <your_compartment_name>
 
 See also:
 

docs/source/user_guide/jobs/run_git.rst

@@ -3,7 +3,6 @@ Run Code from Git Repo
 
 The :py:class:`~ads.jobs.GitPythonRuntime` allows you to run source code from a Git repository as a job.
 
-.. include:: ../jobs/toc_local.rst
 
 PyTorch Example
 ===============

docs/source/user_guide/jobs/run_notebook.rst

@@ -3,7 +3,6 @@ Run a Notebook
 
 The :py:class:`~ads.jobs.NotebookRuntime` allows you to run a single Jupyter notebook as a job.
 
-.. include:: ../jobs/toc_local.rst
 
 TensorFlow Example
 ==================

docs/source/user_guide/jobs/run_python.rst

@@ -6,7 +6,6 @@ You can configure the environment variables, command line arguments, and conda e
 as described in :doc:`infra_and_runtime`. This section shows the additional enhancements provided by
 :py:class:`~ads.jobs.PythonRuntime`.
 
-.. include:: ../jobs/toc_local.rst
 
 Example
 =======

docs/source/user_guide/jobs/tabs/python_runtime.rst

@@ -92,7 +92,6 @@
           - other_packages
           scriptPathURI: local/path/to/code_dir
           workingDir: code_dir
-          workingDir: code_dir
 
 
 .. code-block:: python