From 7b28a16f7a527f22b31c3ea61ecd7abbc3c8c8cf Mon Sep 17 00:00:00 2001 From: "W. Trevor King" Date: Thu, 26 May 2016 22:43:03 -0700 Subject: [PATCH] runtime: Consistent indent for "However, some actions..." The shorter-than-normal (for the rest of this list) indent landed with the line in be594153 (Split create and start, 2016-04-01, #384). Signed-off-by: W. Trevor King --- runtime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/runtime.md b/runtime.md index 1280a1f33..8da4dbbb2 100644 --- a/runtime.md +++ b/runtime.md @@ -38,7 +38,7 @@ The lifecycle describes the timeline of events that happen from when a container While the resources requested in the [`config.json`](config.md) MUST be created, the user-specified code (from [`process`](config.md#process-configuration) MUST NOT be run at this time. Any updates to `config.json` after this step MUST NOT affect the container. 3. Once the container is created additional actions MAY be performed based on the features the runtime chooses to support. - However, some actions might only be available based on the current state of the container (e.g. only available while it is started). + However, some actions might only be available based on the current state of the container (e.g. only available while it is started). 4. Runtime's `start` command is invoked with the unique identifier of the container. The runtime MUST run the user-specified code, as specified by [`process`](config.md#process-configuration). 5. The container's process is stopped.