Deployed dc1352d with MkDocs version: 1.1.2

misc/pelican/index.html

@@ -468,12 +468,14 @@ <h1>Pelican</h1>
                 <h2 id="uprade-of-osdf-to-pelican-for-collaborations">Uprade of OSDF to Pelican for Collaborations<a class="headerlink" href="#uprade-of-osdf-to-pelican-for-collaborations" title="Permanent link">&para;</a></h2>
 <p>The OSG Collab AP had an OSDF door deployed on the access point that provided users with authenticated access to a Ceph storage cluster for shared projects from HTCondor jobs to the OSPool running at remote Execution Points (EPs). Users running jobs on the OSPool access the filesystem either via a client tool (stashcp) or via an HTCondor plugin that is invoked in their submit scripts. The storage is also mounted on the AP at /ospool/uc-shared/project. </p>
 <p>The general purpose documentation found here (https://portal.osg-htc.org/documentation/htc_workloads/managing_data/osdf/) is also applicable for the users on the OSG Collab AP. It describes using the HTCondor plugin to move data to and from the OSDF Origin. 
-In a nutshell:
-  1. Use this for your job running on the OSPool to a file from your project directory:
-  transfer_input_files = osdf:///ospool/apXX/data/<username>/<file>
-  2. Use this for your jobs running on the OSPool to write a file into your project directory:
+In a nutshell, if you are not using the client tool then:</p>
+<ol>
+<li>Use this for your job running on the OSPool to a file from your project directory:
+  transfer_input_files = osdf:///ospool/apXX/data/<username>/<file></li>
+<li>Use this for your jobs running on the OSPool to write a file into your project directory:
   OSDF_LOCATION = osdf:///ospool/
-  transfer_input_files = $(OSDF_LOCATION)/<file></p>
+  transfer_input_files = $(OSDF_LOCATION)/<file></li>
+</ol>