github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Typo fixes (#2193) 

* Fix typo in README.md

Signed-off-by: Daniel Lemm <61800298+ffe4@users.noreply.github.com>

* Fix typo in CONTRIBUTING.md

Signed-off-by: Daniel Lemm <61800298+ffe4@users.noreply.github.com>
pull/2199/head^2
Daniel 2020-09-04 19:17:15 +02:00 committed by GitHub
parent 4c3ec907ab
commit 4954923097
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CONTRIBUTING.md
View File

@ -12,7 +12,7 @@ If you're interested in contributing documentation, please note the following:
## Developer Certificate Of Origin ## ## Developer Certificate Of Origin ##
To contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make. The DCO is a simple statement that you, as a contributor, have the legal rite to make the contribution. To contribute to this project, you must agree to the Developer Certificate of Origin (DCO) for each commit you make. The DCO is a simple statement that you, as a contributor, have the legal right to make the contribution.
See the [DCO](DCO) file for the full text of what you must agree to. See the [DCO](DCO) file for the full text of what you must agree to.

2
README.md
View File

@ -70,7 +70,7 @@ There are two major ways that K3s is lighter weight than upstream Kubernetes:
1. The memory footprint to run it is smaller 1. The memory footprint to run it is smaller
2. The binary, which contains all the non-containerized components needed to run a cluster, is smaller 2. The binary, which contains all the non-containerized components needed to run a cluster, is smaller
The memory footprint is reduced primarily by running many components inside of single process. This eliminates significant overhead that would otherwise be duplicated for each component. The memory footprint is reduced primarily by running many components inside of a single process. This eliminates significant overhead that would otherwise be duplicated for each component.
The binary is smaller by removing third-party storage drivers and cloud providers, which is explained in more detail below. The binary is smaller by removing third-party storage drivers and cloud providers, which is explained in more detail below.