alexvanin/certificates
1
0
Fork 0
forked from TrueCloudLab/certificates
Code Pull requests Activity

Merge pull request #78 from smallstep/typo-fixes

Browse source 
Bunch of typos and misformatting
This commit is contained in:
Mariano Cano 2019-06-11 10:55:14 -07:00 committed by GitHub
commit fb4d114a82
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
6 changed files with 10 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
README.md
View file

@ -330,9 +330,10 @@ you are interested in. Ex: `step help ca provisioners list`.
3. On the web at https://smallstep.com/docs/certificates.
4. On your browser by running `step ca help --http :8080` from the command line
4. On your browser by running `step help --http=:8080 ca` from the command line
and visiting http://localhost:8080.
## The Future
We plan to build more tools that facilitate the use and management of zero trust

4
docs/CONTRIBUTING.md
View file

@ -16,7 +16,7 @@ to manage issues, etc.
## Asking Support Questions
Users and developers can ask questions over email (info@smallstep.com) or
[twitter](https://twitter.com/smallsteplabs). Please don't use the GitHub
[twitter](https://twitter.com/smallsteplabs). Please don't use the GitHub
issue tracker to ask questions.
## Reporting Issues
@ -29,7 +29,7 @@ certificates` in use (`step-ca version`) and your operating system.
## Code Contribution
'step certificates` aims to become a fully featured online Certificate
`step certificates` aims to become a fully featured online Certificate
Authority. We encourage all contributions that meet the following criteria:
* fit naturally into a Certificate Authority.

5
docs/GETTING_STARTED.md
View file

@ -1,6 +1,6 @@
# Getting Started
Demonstrates setting up your own PKI and certificate authority using `step ca`
Demonstrates setting up your own public key infrastructure (PKI) and certificate authority (CA) using `step ca`
and getting certificates using the `step` command line tool and SDK.
Check out [Getting started with docker](docker.md) to run [step certificates](https://github.com/smallstep/certificates)
@ -364,7 +364,7 @@ $ bin/step ca provisioner list
```
Now let's `reload` the CA. You will need to re-enter your intermediate
password unless it's in your `ca.json` or your are using `--password-file`.
password unless it's in your `ca.json` or you are using `--password-file`.
```
$ ps aux | grep step-ca # to get the PID
@ -609,4 +609,3 @@ are features that we plan to implement, but are not yet available. In the mean
time short lived certificates are a decent alternative.
* Keep your hosts secure by enforcing AuthN and AuthZ for every connection. SSH
access is a big one.

2
docs/docker.md
View file

@ -61,7 +61,7 @@ cli](https://github.com/smallstep/cli#installation-guide).
5. Place the PKI root password in a known location.
Our image is expecting the password to be placed in `/home/step/secrets/password`
you can simple go in to the terminal again and write that file:
you can simply go in to the terminal again and write that file:
```sh
$ docker run -it -v step:/home/step smallstep/step-ca sh

2
docs/provisioners.md
View file

@ -6,7 +6,7 @@ can be used to authenticate with the CA and get a certificate.
## JWK
JWK is the default provisioner type. It uses public-key cryptography sign and
JWK is the default provisioner type. It uses public-key cryptography to sign and
validate a JSON Web Token (JWT).
The [step](https://github.com/smallstep/cli) CLI tool will create a JWK

2
docs/questions.md
View file

@ -108,7 +108,7 @@ automated method as your system grows.
Absolutely. [Details here].
## Furher Reading
## Further Reading
* [Use TLS Everywhere](https://smallstep.com/blog/use-tls.html)
* [Everything you should know about certificates and PKI but are too afraid to ask](https://smallstep.com/blog/everything-pki.html)