minor cleanup

	modified:   docs/hpc/01_getting_started/01_intro.md
	modified:   docs/hpc/01_getting_started/02_getting_and_renewing_an_account.md
	modified:   docs/hpc/01_getting_started/03_walkthrough_approve_hpc_account_request.md
	modified:   docs/hpc/01_getting_started/04_walkthrough_renew_hpc_account_iiq.md
	modified:   docs/hpc/01_getting_started/05_hpc_accounts_external_collaborators.md
	renamed:    docs/hpc/03_navigating_the_cluster/linux_tutorial.md -> docs/hpc/03_navigating_the_cluster/01_linux_tutorial.mdx
	renamed:    docs/hpc/03_navigating_the_cluster/hpc_foundations.md -> docs/hpc/03_navigating_the_cluster/02_hpc_foundations.mdx
	deleted:    docs/hpc/03_navigating_the_cluster/navigating_the_cluster.md

Author: s-sajid-ali

docs/hpc/01_getting_started/01_intro.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 1
----
-
 # Start here!
 
 Welcome to the Frances HPC documentation! If you do not have an HPC account, please proceed to the next section that explains how you may be able to get one.

docs/hpc/01_getting_started/02_getting_and_renewing_an_account.md

@@ -1,10 +1,5 @@
----
-sidebar_position: 1 
----
-
 # Getting and Renewing an Account
 
-
 [nyu vpn link]: https://www.nyu.edu/life/information-technology/infrastructure/network-services/vpn.html
 
 [nyu ims link]: https://identity.it.nyu.edu/

docs/hpc/01_getting_started/03_walkthrough_approve_hpc_account_request.md

@@ -1,8 +1,3 @@
----
-sidebar_position: 1 
----
-
-
 # How to approve an HPC Account Request
 
 When someone nominates you as their HPC sponsor, you should be notified by email. You can also [log into IIQ at any time](https://iiq.nyu.edu/identityiq), and if you have a request awaiting your approval, it will appear in your "Actions Items" box, as per the following screenshot:

docs/hpc/01_getting_started/04_walkthrough_renew_hpc_account_iiq.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 1 
----
-
 # Renewing your HPC Account with IIQ
 
 Login to the URL given below, using your netid/password, to create or manage HPC Account Requests:

docs/hpc/01_getting_started/05_hpc_accounts_external_collaborators.md

@@ -1,7 +1,3 @@
----
-sidebar_position: 1 
----
-
 # HPC Accounts for Sponsored External Collaborators
 
 External (non-NYU) collaborators can access, with proper sponsorship, the NYU HPC Environment.

…navigating_the_cluster/linux_tutorial.md …gating_the_cluster/01_linux_tutorial.mdxdocs/hpc/03_navigating_the_cluster/linux_tutorial.md renamed to docs/hpc/03_navigating_the_cluster/01_linux_tutorial.mdx docs/hpc/03_navigating_the_cluster/linux_tutorial.md renamed to docs/hpc/03_navigating_the_cluster/01_linux_tutorial.mdx

@@ -1,78 +1,21 @@
----
-toc_max_heading_level: 2
-sidebar_position: 1
----
-
 # Linux Tutorial
 
-- [Getting a new Account on the NYU HPC cluster](#getting-a-new-account-on-the-nyu-hpc-cluster)
-
-- [Getting Started on HPC Greene Cluster](#getting-started-on-hpc-greene-cluster)
-
-- [Available file systems on Greene](#available-file-systems-on-greene)
-
-- [Basic Linux Commands](#basic-linux-commands)
-
-- [Copying, moving or deleting files locally](#copying-moving-or-deleting-files-locally)
-
-- [Text Editor (NANO)](#text-editor-nano)
-
-- [Writing Scripts](#writing-scripts)
-
-- [Setting execute permission with chmod](#setting-execute-permission-with-chmod)
-
-## Getting a new Account on the NYU HPC cluster
-
-It is expected of everyone to have an NYU HPC Cluster Account. If not follow the steps from \[Getting and Renewing an Account page] to apply for a new account.
-
-## Getting Started on HPC Greene Cluster
-
-In a Linux cluster, there are hundreds of computing nodes interconnected by high-speed networks. Linux operating system runs on each of the nodes individually. The resources are shared among many users for their technical or scientific computing purposes.
-
-### The process to log into the Greene Cluster:
-
-**NYU Campus:** From within the NYU network, that is from an on-campus location, or after you have establisehd a VPN connection with the NYU network, you can login to the HPC clusters directly.
-
-**Off-campus:** The host name of Greene is _`greene.hpc.nyu.edu`_. Logging in to Greene is a two-stage process. The HPC clusters (Greene) are not directly visible to the internet (outside the NYU Network). If you are outside NYU's Network (off-campus) you must first login to a bastion host named _`gw.hpc.nyu.edu`_ .
-
-From within the NYU network, that is, from an on-campus location, or after you are in the NYU's network via VPN, you can login to the HPC clusters directly. You do not need to login to the bastion host.
+:::tip[Prerequisites]
+Login to the Greene cluster as described in the section on [connecting to the HPC cluster](../02_connecting_to_hpc/01_connecting_to_hpc.md).
 
-To login into the HPC cluster ( Greene ), simply use:
-
-```sh
-ssh <NYUNetID>@greene.hpc.nyu.edu
-```
-
-- To access from Windows Operating System with PuTTY, please follow the steps at \[Accessing HPC via windows page]
-- Or To connect to VPN from Linux/Mac OS, please follow the steps at \[Accessing HPC via linux/MacOS page]
-
-From an off-campus location or without a VPN (outside NYU-NET), logging in to the HPC clusters is a 2 step process:
-
-1. Frist login to the bastion host, _`gw.hpc.nyu.edu`_. From a Mac or Linux workstation, this is a simple terminal command. Your password is the same password you use for NYU Home:
-
-```sh
-ssh <NYUNetID>@gw.hpc.nyu.edu
-```
-
-_Windows users will need to use Putty, see \[Accessing HPC via windows page]_
-
-2. Next login to the cluster. For Greene, this is done with:
-
-```sh
-ssh <NYUNetID>@greene.hpc.nyu.edu
-```
+:::
 
 ## Available file systems on Greene
 
 Files Systems for usage:
 
 The NYU HPC clusters have multiple file systems for user's file storage needs. Each file system is configured differently to serve a different purpose.
 
-| **Space** | **Environment Variabe** | **Space Purpose** | **Flushed** | **Allocation** (per user) |
+| **Space** | **Environment Variable** | **Purpose** | **Flush Policy** | **Allocation** (per user) |
 | :-- | :-- | :-- | :-- | :-- |
-| `/home` | $HOME | Program Development space; For storing small files, source code, scripts etc that are backed up | NO | 20GB |
-| `/scratch` | $SCRATCH | Computational Workspace; For storing large files/data, infrequent reads and writes | YES Files not accessed for 60 days are deleted | 5TB |
-| `/archive` | $ARCHIVE | Long Term Storage ( Cold storage ) | NO | 2TB |
+| `/home` | `$HOME` | Program Development space; For storing small files, source code, scripts etc that are backed up | NO | 20GB |
+| `/scratch` | `$SCRATCH` | Computational Workspace; For storing large files/data, infrequent reads and writes | YES Files not accessed for 60 days are deleted | 5TB |
+| `/archive` | `$ARCHIVE` | Long Term Storage ( Cold storage ) | NO | 2TB |
 
 ## Basic Linux Commands
 
@@ -143,9 +86,9 @@ If you run "` cd `" with no arguments, you will be returned to your home directo
 | rmdir subdir/ | Remove subdir only if it's empty |
 | rm -r subdir/ | Recursively delete the directory subdir and everything else in it. ` Use it with care ! ` |
 
-## Text Editor (NANO)
+## Text Editor
 
-"nano" is a friendly text editor that can be used to edit the content of an existing file or create a new file. Here are some options used in nano editor.
+`nano` is a friendly text editor that can be used to edit the content of an existing file or create a new file. Here are some options used in nano editor.
 
 | Options | Explanation |
 | :------ | :---------- |
@@ -201,7 +144,10 @@ In Unix, a file has three basic permissions, each of which can be set for three
 
 - Execute permission (" x ") - numeric value 1. 
 
-> **_NOTE:_** When applied to a directory, execute permission refers to whether the directory can be entered with 'cd'
+:::info
+When applied to a directory, execute permission refers to whether the directory can be entered with 'cd'
+
+:::
 
 The three levels of user are:
 
@@ -213,7 +159,10 @@ The three levels of user are:
 
 You grant permissions with "` chmod who+what file `" and revoke them with "` chmod who-what file `". 
 
-> **_NOTICE:_** The first has "+" and the second "-"
+:::info
+The first has "+" and the second "-"
+
+:::
 
 Here "who" some combination of "u", "g" and "o" and what is some combination of "r", "w" and "x". So to set execute permission, as in the example above, we use:
 

…avigating_the_cluster/hpc_foundations.md …ating_the_cluster/02_hpc_foundations.mdxdocs/hpc/03_navigating_the_cluster/hpc_foundations.md renamed to docs/hpc/03_navigating_the_cluster/02_hpc_foundations.mdx docs/hpc/03_navigating_the_cluster/hpc_foundations.md renamed to docs/hpc/03_navigating_the_cluster/02_hpc_foundations.mdx

@@ -1,21 +1,8 @@
----
-toc_max_heading_level: 2
-sidebar_position: 2
----
-
 # HPC Foundations
 
-The goal of this exercise is to help you understand the fundamentals **_A to Z_** on effecively navigating the cluster for your research or academic projects.
-
-Before we begin this exercise please make sure you have access to the NYU HPC cluster, if not please review the [Accessing HPC page](../02_connecting_to_hpc/01_connecting_to_hpc.md).
-
-Login to the Greene cluster with ssh at :
-> Accessible under NYU Net ( either via VPN or within campus network )
-```sh
-greene.hpc.nyu.edu
-```
+The goal of this exercise is to help you understand the fundamentals of effecively navigating the cluster for your research or academic projects. Before we begin this exercise please make sure you have access to the NYU HPC cluster, if not please review the section on [connecting to the HPC cluster](../02_connecting_to_hpc/01_connecting_to_hpc.md).
 
-Once logged in, you should notice the **_node_** which you are currently on from the _bash prompt_ as shown below :
+Login to the Greene cluster as described in the section on [connecting to the HPC cluster](../02_connecting_to_hpc/01_connecting_to_hpc.md). Once logged in, you should notice the **_node_** which you are currently on from the _bash prompt_ as shown below :
 
 ```sh
 [pp2959@log-3 ~]$
@@ -87,10 +74,10 @@ As you can see, it is the same file, same directory, the same filesystem for all
 
 Regardless of whichever login node you may end up on, **_all_** users have access to **_a common_** filesystem that is `/home`. It is important to understand that users read and write files to the same filesystem while logged in from any of the 4 login nodes.
 
-> **_REMEMBER_**
->
-> - `/home` is your `personal workspace` having a limited space
-> - It is intended as a space for `maintaining code bases only`
+:::warning
+-   `/home` is your `personal workspace` having a limited space
+-   It is intended as a space for `maintaining code bases only`
+:::
 
 Now, `exit` from your current `shell instance` by running the command `exit`:
 
@@ -100,15 +87,17 @@ logout
 Connection to log-1 closed.
 [pp2959@log-3 ~]$ 
 ```
+::::info
+1.  The first line tells you that you have logged out of your current **_bash shell_**
+2.  The second line tells you that the **_ssh connection_** to log-1 has been **_closed_** 
+3.  Now you are back to your **_previous login_** node, in this example log-3, that is your previous **_bash shell_**
 
-> **IMPORTANT - _Notice the output:_**
->
-> 1. The first line tells you that you have logged out of your current **_bash shell_**
-> 2. The second line tells you that the **_ssh connection_** to log-1 has been **_closed_** 
-> 3. Now you are back to your **_previous login_** node, in this example log-3, that is your previous **_bash shell_**
->
-> **_Why is this imporatant to understand_** ? 
-> Because this will build your foundations in understanding the different kinds of nodes that exists and how you should use them for your projects 
+:::tip[Why is this imporatant to understand?]
+Because this will build your foundations in understanding the different kinds of nodes that exists and how you should use them for your projects
+
+:::
+
+::::
 
 ### Other File Systems
 
@@ -157,7 +146,7 @@ The `/archive` Space:
 
 - Never purged 
 
-## Running programs on a `login` node
+## Running programs on a login node
 
 Login nodes. As the name implies are used for interacting with the cluster only. They are not equiped with compute heavy hardware or much memory, and hence you may run simple programs ( that can lag a bit ) but not compute heavy workloads. 
 
@@ -234,8 +223,7 @@ As you can see, we encounter an error like the one below:
 [pp2959@log-3 ~]$
 ```
 
-`apt-get` does not exist, this is because package managers are not allowed on the cluster as they require `root` privileges for installation.
-You will need to load pre-installed software pacakges with a command called `module`. 
+`apt-get` is not available to users as it requires `root` priviliges which the users do not get.You will need to load pre-installed software pacakges with a command called `module`. 
 
 First, let's search for any versions of `lua` available by running the command `module spider <Software_Package>`:
 
@@ -371,7 +359,7 @@ module --help
 > - `/home` filesystem and it's purpose
 > - Load necessary `modules` to run our programs
 
-## Running Programs on a `Compute` Node
+## Running Programs on a compute node
 
 The Greene cluster has over 100s of compute nodes equiped with all kinds of High Performance hardware such as x86 Intel, AMD server CPUs, and Nvidia, AMD server GPUs ( such as the H100s ).
 
@@ -413,16 +401,14 @@ cm001.hpc.nyu.edu
 hello, world
 [pp2959@log-2 ~]$
 ```
+:::info
+**_Read the Output carefully_**
+-   This job is given an **_id_** that is `55744835`, this is called a `job id`.
+-   The job `job 55744835` is `queued and waiting` to be scheduled on a compute node, since these nodes are expected to be busy based on demand, it may take some time for your job to be scheduled 
+-   Once the `job` gets `scheduled`, your program `lua hello.lua` gets run on a chosen `compute node(s)` and the program's output is printed back to your console 
+-   Based on your output, you may notice the name of the compute node that this program runs on, the node `cm001.hpc.nyu.ed` in this example is a CPU only node, you may notice a different node. You can find more details about the \[specific nodes here].
 
-> **_Read the Output carefully_**
->
-> 1. This job is given an **_id_** that is `55744835`, this is called a `job id`.
-> 
-> 2. The job `job 55744835` is `queued and waiting` to be scheduled on a compute node, since these nodes are expected to be busy based on demand, it may take some time for your job to be scheduled 
-> 
-> 3. Once the `job` gets `scheduled`, your program `lua hello.lua` gets run on a chosen `compute node(s)` and the program's output is printed back to your console 
-> 
-> 4. Based on your output, you may notice the name of the compute node that this program runs on, the node `cm001.hpc.nyu.ed` in this example is a CPU only node, you may notice a different node. You can find more details about the \[specific nodes here].
+:::
 
 **_Now how do we determine Or specify the amount of resources needed to run our `hello.lua` script ?_**
 
@@ -1346,7 +1332,3 @@ salloc: Job allocation 56149430 has been revoked.
 ## Package Software with `Containers`
 
 ## Burst priority jobs to Cloud with `Burst nodes`
-
-## `Secure Research Data` Environments
-
-