Reworded language; updated the SSH fingerprint

- Reworded language in writing-support-requests.md
- Updated the SSH fingerprint on the FAQ page
- Other minor changes

help/faq.md

@@ -8,40 +8,36 @@ sort: 1
 
 ### I forgot my password - what now?
 
-You can reset it here: <https://www.metacenter.no/user/>
+You can reset it here: [link to be provided]
 
 ### How do I change my password on Star?
 
-The password can be changed on the [password metacenter
-page](https://www.metacenter.no/user/password/), log in using your
-username on Star and the NOTUR domain.
+The password can be changed on the [password reset page](#). Log in using
+your username on Star.
 
 The `passwd` command known from other Linuxes does not work. The Star
 system is using a centralised database for user management. This will
 override the password changes done locally on Star.
 
-### What is the ssh key fingerprint for star.uit.no?
+### What is the ssh key fingerprint for star.hofstra.edu?
 
 The SHA256 key fingerprint is:
-`SHA256:YJpwZ91X5FNXTc/5SE1j9UR1UAAI4FFWVwNSoWoq6Hc`
+`SHA256:W0NKVfQBl5FeOlOkoEIKIVsp1+47yIvzJAYMx6ECpwM`
 
-The MD5 key fingerprint is:
-`MD5:36:a8:c5:f3:21:24:bb:bc:07:6f:af:4a:fe:3e:cb:9a`
-
-If you are more of a visual person, use
-`ssh -o VisualHostKey=yes star.uit.no` and compare it to this visual
+If you are more of a visual person, run
+`ssh -p 5010 -o VisualHostKey=yes binary.star.hofstra.edu` and compare it to this visual
 key:
 
-    +---[RSA 1024]----+
-    |      oo+ooo**BO^|
-    |     . + ..+ o.BO|
-    |  . . * . o . +.=|
-    |   o * . . . . o.|
-    |    o   S     . .|
-    |   .   o         |
-    |  . . .          |
-    | .  ..E          |
-    |  .. .           |
+    +--[ED25519 256]--+
+    |E + ++  . .o=.+=.|
+    |o=.=o..o . . +ooo|
+    |* +o .. o o  .o+ |
+    |+o    .. +    =  |
+    |..   .  S o    o |
+    | .    .  o .     |
+    |  o... ..        |
+    | ..+o o          |
+    |  .oo. .         |
     +----[SHA256]-----+
 
 ## Installing software

help/writing-support-requests.md

@@ -10,24 +10,24 @@ to understand each problem is at a premium. The easier it is to
 understand yours, the faster we will get to it. Below is a list of good
 practices.
 
-## Never send support requests to staff members directly
+## Never send support requests directly to staff members
 
-Always send them to <support@starhpc.hofstra.io> and staff members will pick
-them up there. On <support@starhpc.hofstra.io> they get tracked and have
-higher visibility. Some staff members work on the support line only part
-time. Sending the request to <support@starhpc.hofstra.io> makes sure that
-somebody will pick it up. Please note in the request that it is about
-Star, as there are more clusters that are handled with this email
-address.
+Please do not contact your cluster administrator directly. Always send
+requests and inquiries to <support@starhpc.hofstra.io> for the quickest
+response. On <support@starhpc.hofstra.io>, requests get tracked and have
+higher visibility. Some of our staff members only work part time.
+Sending the request to <support@starhpc.hofstra.io> makes sure that
+somebody will pick it up. Please note in the request that it is for Star,
+as there are other systems that are managed by us.
 
-## Do not manhandle us as simple "Let me Google that for you" assistants
+## Do not treat us as simple "Let me Google that for you" assistants
 
 Seriously: have you searched the internet with the exact error message
 and the name of your application...? Other scientists may have had the
 very same problem and might have been successful in solving it. By the
-way: that's almost always how we start to research, too...
+way, that's almost always how we start to research issues too!
 
-## Give descriptive subject
+## Give a descriptive subject
 
 Your subject line should be descriptive. "Problem on Star" is not a
 good subject line since it could be valid for basically every support
@@ -35,7 +35,7 @@ email we get. The support staff is a team. The subjects are the first
 thing that we see. We would like to be able to classify emails according
 to subjects before even opening the email.
 
-## Include actual commands and error messages
+## Include the actual commands and error messages
 
 We cover this below, but it's so important it needs to be mentioned at
 the top, too: include the actual command you run and actual error
@@ -81,7 +81,7 @@ achieve. Solving Y can take a long time. We have had cases where after
 enormous effort on Y we realized that the user wanted X and that Y was
 not the best way to achieve X.
 
-## Tell us also what worked
+## Also tell us what worked
 
 Rather often we get requests of the type "I cannot get X to run on two
 nodes". The request then does not mention whether it worked on one node

jobs/job-submission.md

-# Submitting Jobs
+# Creating and Submitting Jobs
 
 In High-Performance Computing (HPC) environments, jobs are submitted to a job scheduler for dispatch and execution on the cluster. Jobs are typically non-interactive and may be queued for batch processing, based on demand and resource availability.
 

quickstart/about-star.md

@@ -6,7 +6,7 @@ sort: 1
 
 ## Overview
 
-Star HPC Cluster is a computing facility designed for a variety of research and computational tasks. Combining advanced computing **nodes** and high-speed **storage systems** with a suite of **software applications**. 
+The Star HPC Cluster is a computing facility designed for a variety of research and computational tasks. It combines advanced computing **nodes** and a high-speed **storage system** with a suite of **software applications**.
 
 SLURM (Simple Linux Utility for Resource Management) is our chosen job scheduler and queueing system that efficiently manages resource allocation, ensuring everyone gets the right amount of resources at the right time.