Skip to content

Commit a48397b

Browse files
committed
Remove trailing whitespace
With: $ sed -i 's/ *$//' *.md *.go Signed-off-by: W. Trevor King <[email protected]>
1 parent 94c1803 commit a48397b

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ With Standard Containers we can put an end to that embarrassment, by making INDU
5757
Development happens on GitHub for the spec.
5858
Issues are used for bugs and actionable items and longer discussions can happen on the [mailing list](#mailing-list).
5959

60-
The specification and code is licensed under the Apache 2.0 license found in the `LICENSE` file of this repository.
60+
The specification and code is licensed under the Apache 2.0 license found in the `LICENSE` file of this repository.
6161

6262
## Discuss your design
6363

runtime-config-linux.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
## Linux namespaces
22

3-
A namespace wraps a global system resource in an abstraction that makes it
4-
appear to the processes within the namespace that they have their own isolated
5-
instance of the global resource. Changes to the global resource are visible to
6-
other processes that are members of the namespace, but are invisible to other
3+
A namespace wraps a global system resource in an abstraction that makes it
4+
appear to the processes within the namespace that they have their own isolated
5+
instance of the global resource. Changes to the global resource are visible to
6+
other processes that are members of the namespace, but are invisible to other
77
processes. For more information, see [the man page](http://man7.org/linux/man-pages/man7/namespaces.7.html)
88

9-
Namespaces are specified in the spec as an array of entries. Each entry has a
10-
type field with possible values described below and an optional path element.
9+
Namespaces are specified in the spec as an array of entries. Each entry has a
10+
type field with possible values described below and an optional path element.
1111
If a path is specified, that particular file is used to join that type of namespace.
1212

1313
```json

0 commit comments

Comments
 (0)