Skip to content

Commit b5a5f94

Browse files
authored
Merge pull request #245 from chu11/lets
tutorials/flux-jobs: Fix invalid contractions
2 parents 7333171 + 0d149a7 commit b5a5f94

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

tutorials/commands/flux-jobs.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -255,7 +255,7 @@ For most users, instead of formatting your own output, you may wish to use one o
255255
long Extended flux-jobs format string
256256
deps Show job urgency, priority, and dependencies
257257
258-
For example, lets take a look at the ``long`` output.
258+
For example, let's take a look at the ``long`` output.
259259

260260
.. code-block:: console
261261
@@ -298,8 +298,8 @@ Recursive Job Listing
298298
This section is independent on the previous one. To continue on with this example from the previous one,
299299
you may wish to cancel your jobs from before via ``flux cancel --all``.
300300

301-
By default, ``flux jobs`` will not list jobs that are running under subinstances within Flux. Lets illustrate
302-
this with an example. Lets submit the following script to ``flux batch``.
301+
By default, ``flux jobs`` will not list jobs that are running under subinstances within Flux. Let's illustrate
302+
this with an example. Submit the following script to ``flux batch``.
303303

304304
.. code-block:: sh
305305
#!/bin/sh
@@ -312,7 +312,7 @@ this with an example. Lets submit the following script to ``flux batch``.
312312
All we're doing is running two ``sleep`` jobs for infinity, and then calling ``flux queue drain`` to wait for those
313313
jobs to complete. (See :ref:`Waiting for jobs<waiting-for-jobs>` tutorial for info on using ``flux queue drain`` to wait for jobs to complete.)
314314

315-
Lets run this via ``flux batch``
315+
Let's run this via ``flux batch``
316316

317317
.. code-block:: console
318318

0 commit comments

Comments
 (0)