Skip to content

Fix redundant wording #1420

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 19, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/networking/dns/using-your-systems-hosts-file.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ There are many different ways to use entries in the hosts file, and the types of

0.0.0.0 example.com

- Set a [fully qualified domain name](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (FQDN). In the example below, replace *example_hostname* with your system's hostname. The domain *example.com* can be a public internet domain (ex. a public website) or the domain of a private network (ex. your home LAN), or a subdomain (subdomain.example.com). It's important to add the FQDN entry directly after the localhost line, so the end result would look like:
- Set a [fully qualified domain name](https://en.wikipedia.org/wiki/Fully_qualified_domain_name) (FQDN). In the example below, replace *example_hostname* with your system's hostname. The domain *example.com* can be a public internet domain (ex. a public website) or the domain of a private network (ex. your home LAN), or a subdomain (subdomain.example.com). It's important to add the FQDN entry directly after the localhost line, so it looks like:

127.0.0.1 localhost
127.0.1.1 hostname.example.com example_hostname
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -621,7 +621,7 @@ To verify the rules are applied and available after the system reboot use the co

## Network Lock-out

When you're applying network rules, especially with both IPv4 and IPv6 and multiple interfaces, it is easy to lock yourself out. In the event you apply the rule and are unable to access your server, you may gain access through [Lish](https://www.linode.com/docs/networking/using-the-linode-shell-lish) in the Linode Manager. The following steps will guide you through using the GUI interface of your Linode to gain access to your server:
When you're applying network rules, especially with both IPv4 and IPv6 and multiple interfaces, it is easy to lock yourself out. In the event you apply the rule and are unable to access your server, you may gain access through [Lish](https://www.linode.com/docs/networking/using-the-linode-shell-lish) in the Linode Manager. The following steps will guide you through using the graphical interface of your Linode to gain access to your server:

1. Connect to your Linode Manager.
2. Click on the Remote Access tab.
Expand Down
2 changes: 1 addition & 1 deletion docs/websites/cms/install-odoo-10-on-ubuntu-16-04.md
Original file line number Diff line number Diff line change
Expand Up @@ -276,7 +276,7 @@ The most relevant line in this file is `StandardOutput=journal+console`. As conf

## Test Odoo

1. Open a new browser window and enter in the address bar:
1. Open a new browser window and visit the address:

http://<your_domain_or_IP_address>:8069

Expand Down