chore: wording

rokroskar · rokroskar · commit 1492ffd53744 · 2026-07-28T10:51:20.000-06:00
diff --git a/docs/docs/10-users/60-compute/10-launcher.md b/docs/docs/10-users/60-compute/10-launcher.md
@@ -2,7 +2,7 @@
 
 A launcher is a component of a project that defines how compute runs on RenkuLab. Each launcher combines an [Environment](environment) with a default [Resource Pools & Classes](resource-pools-and-classes) configuration.
 
-Renku supports two types of launcher:
+Renku supports two types of launchers:
 
 1. **Session launcher:** launches an interactive, browser-based [Session](session) for coding and data exploration.
 2. **Job launcher:** runs a non-interactive [Job](job) in the background when you submit it.
@@ -13,18 +13,18 @@ Renku supports two types of launcher:
 
 A launcher contains:
 
-1. an [Environment](environment), which defines the software installed in the run, and
-2. a default resource class (see [Resource Pools & Classes](resource-pools-and-classes)), which determines the compute resources available.
+1. an [Environment](environment), which defines the software packages and libraries used by the session or job, and
+2. a default resource class (see [Resource Pools & Classes](resource-pools-and-classes)), which determines the availabler compute resources.
 
 For a Job launcher, you also configure a **job command** that defines what runs when the job is submitted.
 
-Project's launchers are usable to everyone who can see the project. Anyone with access can launch a session or submit a job from a launcher configured in the project.
+Project's launchers are usable to everyone who can see the project. Anyone with access to the project can launch a session or submit a job from a launcher.
 
 However, the sessions you launch and the jobs you submit are only accessible to you. They are not shared across users.
 
 :::info
 
-A third type of launcher, namely an **App Launchers**, will be available by October 2026.
+**App Launchers** will be available in October 2026.
 
 :::
 
@@ -33,4 +33,4 @@ A third type of launcher, namely an **App Launchers**, will be available by Octo
 ## Next steps
 
 - To create an interactive session launcher, see [Add a session launcher to your project](session/guides/add-a-session-launcher-to-your-project).
-- To create a job launcher, see [Add a job launcher to your project](job/guides/create-a-job-launcher).
+- To create a job launcher, see [Add a job launcher to your project](job/guides/create-a-job-launcher).
diff --git a/docs/docs/10-users/60-compute/50-session/index.md b/docs/docs/10-users/60-compute/50-session/index.md
@@ -1,9 +1,10 @@
 # Session
 
-A Renku session is a running interactive run-time environment that can be used to do work on data and code.
+A Renku session is an interactive run-time environment that can be used to do work on data and code.
 
-A session is created by a **Session Launcher** (see [Launcher](../launcher)) and is a running instance of an [Environment](../environment). Inside a session, all of the project’s [Code repository](../../code/code-repository)s are cloned and [Data connector](../../data/data)s are mounted (as long as the user provided any required access credentials).
+A session is created by a **Session Launcher** (see [Launcher](../launcher)) and is a running instance of an [Environment](../environment). Inside a session, all of the project’s [Code repositories](../../code/code-repository) are cloned and [Data connectors](../../data/data) are mounted (as long as the user provided any required access credentials).
 
-A session has access to a certain amount of compute resources (CPU, GPU, RAM and storage). This is determined by the resource pool set on [Launchers](../launcher). For more information about compute resources, see [Resource Pools & Classes](../resource-pools-and-classes).
+A session has access to a certain amount of compute resources (CPU, GPU, RAM and storage). This is determined by the resource class set on the [Launcher](../launcher). For more information about compute resources, see [Resource Pools & Classes](../resource-pools-and-classes).
 
-The sessions you launch are always private to you.
+The sessions you launch are always private to you, but others with access to your project may launch their own instances
+of the session.
diff --git a/docs/docs/10-users/60-compute/60-job/guides/10-create-a-job-launcher.md b/docs/docs/10-users/60-compute/60-job/guides/10-create-a-job-launcher.md
@@ -10,7 +10,7 @@ Job launchers do not support **global environments**. You must use **Create from
 
 ## Create a job launcher
 
-1. In the **Sessions** section of the project page, click **+** to add a new launcher.
+1. In the **Launchers** section of the project page, click **+** to add a new launcher.
 
 <p class="image-container-l">
 ![JobLauncher](./job-creation-10.png)
@@ -24,7 +24,7 @@ Job launchers do not support **global environments**. You must use **Create from
 
 3. Choose and configure an **environment**:
    - **Create from code** — Renku builds an environment from a code repository (for example, one with an `environment.yml` or `requirements.txt`). See [How to create an environment with custom packages installed](../../environment/guides/create-environment-with-custom-packages-installed).
-   - **Custom image** — use your own Docker image. See [How to use your own docker image for a Renku session](../../environment/guides/use-your-own-docker-image-for-renku-session).
+   - **External environment** — use your own Docker image. See [How to use your own docker image for a Renku session](../../environment/guides/use-your-own-docker-image-for-renku-session).
 
 <p class="image-container-l">
 ![JobLauncher](./job-creation-30.png)
diff --git a/docs/docs/10-users/60-compute/60-job/guides/20-submit-a-job.md b/docs/docs/10-users/60-compute/60-job/guides/20-submit-a-job.md
@@ -22,11 +22,11 @@ See [How to configure a session secret](../../guides/configure-session-secret) f
 
 2. Review the environment summary in the **Review and submit job** modal.
 
-<p class="image-container-l">
+<p class="image-container-m">
 ![JobLauncher](./job-submission-20.png)
 </p>
 
-3. Enter a **Submission ID**, that is a short unique name for this job run (for example, `run-a1b2c3`). Renku suggests one automatically; you can edit it.
+3. Enter a **Submission ID**, that is a short unique name for this job run (for example, `run-a1b2c3`). Renku suggests one automatically but you can edit it before submitting the job.
 
    The submission ID must:
    - Start with a lowercase letter
@@ -44,7 +44,7 @@ See [How to configure a session secret](../../guides/configure-session-secret) f
 7. Click **Submit job**.
 
 <p class="image-container-l">
-![JobLauncher](./job-submission-30.png)
+![JobLauncher](job-submission-30.png)
 </p>
 
 You can submit multiple jobs from the same launcher at the same time. Each job must have its own submission ID.
diff --git a/docs/docs/10-users/60-compute/60-job/guides/30-monitor-cancel-and-dismiss-jobs.md b/docs/docs/10-users/60-compute/60-job/guides/30-monitor-cancel-and-dismiss-jobs.md
@@ -8,7 +8,7 @@ Your active and recent jobs appear in several places:
 
 - **Under the job launcher** on the project page — each row shows the submission ID and status
 - **In the launcher side panel** — open the launcher to see **Your submitted jobs**
-- **On your dashboard** — jobs are listed alongside interactive sessions
+- **On your dashboard** — jobs are listed just below interactive sessions
 
 <p class="image-container-l">
 ![JobLauncher](./job-monitoring-10.png)
@@ -32,8 +32,6 @@ While a job is **Starting**, **Running**, **Completed**, or **Errored**, click *
 ![JobLauncher](./job-monitoring-20.png)
 </p>
 
-<!-- TODO: screenshot monitor-cancel-and-dismiss-jobs-30.png — View logs for a running job -->
-
 Logs are available for 24 hours or until you dismiss the job.
 
 ## Cancel a running job
diff --git a/docs/docs/10-users/60-compute/60-job/index.md b/docs/docs/10-users/60-compute/60-job/index.md
@@ -2,7 +2,7 @@
 
 A Renku job is a non-interactive run that executes a command in the background using a project's [Environment](../environment) and compute resources.
 
-A job is submitted from a **Job launcher** (see [Launcher](../launcher)) and runs without a browser-based interface. Inside the job, all of the project's [Code repository](../../code/code-repository)s are cloned and [Data connector](../../data/data)s are mounted, as long as you provided any required access credentials when submitting.
+A job is submitted from a **Job launcher** (see [Launcher](../launcher)) and runs without a browser-based interface. Inside the job, all of the project's [Code repositories](../../code/code-repository) are cloned and [Data connectors](../../data/data) are mounted, as long as you provided any required access credentials when submitting.
 
 Each job submission is identified by a **submission ID** — a short name you choose (or accept from the auto-generated default) that must be unique among your jobs on that launcher. You use the submission ID to tell jobs apart when several are running at once.
 
@@ -14,11 +14,11 @@ The jobs you submit are always private to you. Jobs are not shared between users
 
 A job moves through states such as **Starting**, **Running**, **Completed**, and **Errored**. While a job is starting or running, you can view its logs or cancel it. When a job has completed or errored, you can view its logs and then **Dismiss** it to remove it from your project and dashboard.
 
-Dismissing a job permanently removes it from the RenkuLab interface. You will not be able to reopen its logs after dismissing it.
+Dismissing a job permanently removes it from RenkuLab. You will not be able to reopen its logs after dismissing it.
 
 :::note
 
-Completed and errored jobs are typically removed automatically after about 24 hours if you have not dismissed them. This retention period may change in the future.
+Completed and errored jobs are typically removed automatically after 24 hours if you have not dismissed them.
 
 :::
 
