zydronium/google-nomulus
1
0
Fork 0
mirror of https://github.com/google/nomulus.git synced 2025-04-30 03:57:51 +02:00
Code Issues Projects Releases Packages Wiki Activity

(docs): fixed small errors (#572)

Browse source 
* Update first-steps-tutorial.md

* Update proxy-setup.md (#1)

* Update registrar-faq.md (#2)

* Update first-steps-tutorial.md
This commit is contained in:
0xflotus 2020-05-11 16:01:47 +02:00 • committed by GitHub
parent 763a9573ee
commit 223832a402
3 changed files with 4 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
docs/first-steps-tutorial.md
View file

@ -52,7 +52,7 @@ Updated 1 entities.
* `create_tld` is the subcommand to create a TLD. The TLD name is "example" * `create_tld` is the subcommand to create a TLD. The TLD name is "example"
which happens to be an ICANN reserved string, and therefore "example" can which happens to be an ICANN reserved string, and therefore "example" can
never be created on the Internet at large. never be created on the Internet at large.
* `--initial_tld_state` defines the intital state of the TLD. * `--initial_tld_state` defines the initial state of the TLD.
`GENERAL_AVAILABILITY`, in the case of our example, allows you to `GENERAL_AVAILABILITY`, in the case of our example, allows you to
immediately create domain names by bypassing the sunrise and landrush domain immediately create domain names by bypassing the sunrise and landrush domain
registration periods. registration periods.
@ -168,7 +168,7 @@ $ nomulus -e alpha create_domain fake.example --client acme --admins abcd1234 \
Where: Where:
* `create_domain` is the subcommand to create a domain name. It accepts a * `create_domain` is the subcommand to create a domain name. It accepts a
whitespace-separted list of domain names to be created whitespace-separated list of domain names to be created
* `--client` is used to define the registrar. * `--client` is used to define the registrar.
* `--admins` is the administrative contact's id(s). * `--admins` is the administrative contact's id(s).
* `--techs` is the technical contact's id(s). * `--techs` is the technical contact's id(s).

2
docs/proxy-setup.md
View file

@ -523,7 +523,7 @@ $ kubectl create secret generic service-account \
--from-file=service-account-key.json=<service-account-key.json> --from-file=service-account-key.json=<service-account-key.json>
``` ```
More details on using sevice account on GKE can be found More details on using service account on GKE can be found
[here](https://cloud.google.com/kubernetes-engine/docs/tutorials/authenticating-to-cloud-platform). [here](https://cloud.google.com/kubernetes-engine/docs/tutorials/authenticating-to-cloud-platform).
Repeat the same step for all clusters you want to deploy to. Use `gcloud` to Repeat the same step for all clusters you want to deploy to. Use `gcloud` to

2
docs/registrar-faq.md
View file

@ -138,7 +138,7 @@ No, we do not require verification of zone configurations.
Yes, IPv6 addresses are supported. Yes, IPv6 addresses are supported.
**4.9 How many IP adresses can be listed on an in-bailiwick host object?** **4.9 How many IP addresses can be listed on an in-bailiwick host object?**
Ten IP addresses can be listed on an in-bailiwick host object. This limit is for Ten IP addresses can be listed on an in-bailiwick host object. This limit is for
both IPv4 and IPv6 addresses combined. both IPv4 and IPv6 addresses combined.