Skip to content

Commit c260d0f

Browse files
review comments
Signed-off-by: Matt Richerson <matthew.richerson@hpe.com>
1 parent 0e7f862 commit c260d0f

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/guides/user-containers/readme.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ data:
280280
| `data.volumes[].mountPath` | string | Absolute path on the Rabbit node where the storage is mounted |
281281

282282
The external orchestrator can query the resource by workflow name and namespace to discover where
283-
each storage volume is mounted:
283+
each storage volume is mounted.
284284

285285
## Creating a Container Workflow
286286

@@ -355,7 +355,7 @@ overview of the container-related behavior that occurs:
355355
the workflow. In turn, user containers are created and launched by Kubernetes. Containers are
356356
expected to start in this state. If `createContainer: false`, no pods are launched; instead an
357357
[`NnfContainerData`](#nnfcontainerdata) resource is created that records the storage mount paths.
358-
- PostRun: If `createContainer: true`, user containers are expected to complete (non-zero exit)
358+
- PostRun: If `createContainer: true`, user containers are expected to complete (zero exit)
359359
successfully. If `createContainer: false`, the NNF code does not coordinate with the external
360360
container launcher.
361361
- DataOut: No container related activity.

0 commit comments

Comments
 (0)