Skip to content

Commit 764c683

Browse files
Fixing grammar/punctuation in UNIKERNELS.md (nanovms#1345)
1 parent f0c4b11 commit 764c683

File tree

1 file changed

+13
-13
lines changed

1 file changed

+13
-13
lines changed

UNIKERNELS.md

+13-13
Original file line numberDiff line numberDiff line change
@@ -1,30 +1,30 @@
1-
# What is a Unikernel
1+
# What is a Unikernel?
22

3-
A unikernel is a single process system that is specifically designed to
4-
run only one application. It makes it a great fit for modern cloud
5-
environments because of it's performance, security and size.
3+
A unikernel is a single-process system that is specifically designed to
4+
run only one application. It is a great fit for modern cloud
5+
environments because of its performance, security, and size.
66

77
## Single Process
88

99
Linux systems have archaic design concepts rooted in the 1960s from when
1010
machines cost half a million dollars and needed to run multiple programs
11-
for multiple users. Today developers go out of their way to isolated
12-
programs from each other if for no reason other than manageability
11+
for multiple users. Today, developers go out of their way to isolate
12+
programs from each other if for no other reason than manageability
1313
concerns.
1414

15-
A unikernel embraces the single process concept while allowing the use
16-
of multiple threads. For languages such as Go this fits well. For
17-
interpreted languages such as ruby and python developers in these
15+
A unikernel embraces the single-process concept while allowing the use
16+
of multiple threads. For languages such as Go, this fits well. For
17+
interpreted languages such as Ruby and Python, developers in these
1818
languages typically load balance a set of application servers to enable
19-
a greater degree of concurrency. In the unikernel world we do the same
20-
thing but those app servers become full fledged vms and can make use of
21-
existing load balancers without having to do back flips.
19+
a greater degree of concurrency. In the unikernel world, we do the same
20+
thing but those app servers become full-fledged VMs and can make use of
21+
existing load balancers without having to do backflips.
2222

2323
## No Shell/No Users
2424

2525
This is a security design constraint. There is no shell to remotely log
2626
into and there is no concept of users. While OPS has a stubbed/fake user
2727
it is only present to implement underlying libc calls and has no
28-
relevance otherwise. This also means that modern unix permissions don't
28+
relevance otherwise. This also means that modern Unix permissions don't
2929
have much meaning inside of a unikernel because there is only one
3030
program running and no users.

0 commit comments

Comments
 (0)