Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Clean up docs (formatting, typos and so on) #526

Merged
merged 2 commits into from
Sep 18, 2018
Merged

Clean up docs (formatting, typos and so on) #526

merged 2 commits into from
Sep 18, 2018

Conversation

ichernetsky
Copy link
Contributor

No description provided.

@ichernetsky ichernetsky changed the title PTAL: Clean up docs (formatting, typos and so on) Clean up docs (formatting, typos and so on) Sep 13, 2018
README.md Outdated

There are only very few users with access to the private key, and they also have access to a revocation certificate in case the private key leaks.
This repo using code signing. There is an armored, encrypted GPG key in the repo in [build/private.key](build/private.key). This file includes the Mesos-DNS GPG signing key. The passphrase for the key is stored in Circle-CI's environment. This makes it fairly difficult to leak both components without detectable maliciousness.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/using/uses/


First, create a configuration file for nginx named `nginx.json`:
First, create a configuration file for nginx named `nginx.json` with the following context:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/context/content/

@ichernetsky
Copy link
Contributor Author

@jdef can I go ahead and merge the PR? The CI job is failing for unrelated reasons (the linter is not happy).

@jdef jdef merged commit ca483fa into master Sep 18, 2018
@GoelDeepak GoelDeepak deleted the inc/clean-docs branch September 19, 2018 22:09
vixns pushed a commit to vixns/mesos-dns that referenced this pull request Apr 13, 2019
Clean up docs (formatting, typos and so on)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants