openstack/neutron
Code Issues Proposed changes

Stop using non-ascii characters

Browse Source 
Namely, Replace U+2019 RIGHT SINGLE QUOTATION MARK
with U+0027 APOSTROPHE where appropriate.

Change-Id: Iec9e8f85bcddeb90e9a7fb8f845a7923cac38f52
This commit is contained in:
YAMAMOTO Takashi 2017-07-18 17:04:06 +09:00
parent 9449a63021
commit af4bfb35a2
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/admin/config-ipv6.rst
View File

@ -334,9 +334,9 @@ hand, external router ports are allowed to have a dual-stack configuration
with both an IPv4 and an IPv6 address assigned to them.
Neutron project networks that are assigned Global Unicast Address (GUA)
prefixes and addresses don’t require NAT on the neutron router external gateway
prefixes and addresses don't require NAT on the neutron router external gateway
port to access the outside world. As a consequence of the lack of NAT the
external router port doesn’t require a GUA to send and receive to the external
external router port doesn't require a GUA to send and receive to the external
networks. This implies a GUA IPv6 subnet prefix is not necessarily needed for
the neutron external network. By default, a IPv6 LLA associated with the
external gateway port can be used for routing purposes. To handle this

6
doc/source/admin/intro-basic-networking.rst
View File

@ -64,7 +64,7 @@ As mentioned earlier, modern Ethernet networks use switches to
interconnect the network hosts. A switch is a box of networking
hardware with a large number of ports that forward Ethernet frames
from one connected host to another. When hosts first send frames over
the switch, the switch doesn’t know which MAC address is associated
the switch, the switch doesn't know which MAC address is associated
with which port. If an Ethernet frame is destined for an unknown MAC
address, the switch broadcasts the frame to all ports. The switch learns
which MAC addresses are at which ports by observing the traffic. Once
@ -248,9 +248,9 @@ client, or the server will not receive the broadcast. The DHCP server
responds by sending a UDP packet from port 67 to port 68 on the
client. The exchange looks like this:
1. The client sends a discover ("I’m a client at MAC address
1. The client sends a discover ("I'm a client at MAC address
``08:00:27:b9:88:74``, I need an IP address")
2. The server sends an offer ("OK ``08:00:27:b9:88:74``, I’m offering
2. The server sends an offer ("OK ``08:00:27:b9:88:74``, I'm offering
IP address ``192.0.2.112``")
3. The client sends a request ("Server ``192.0.2.131``, I would like
to have IP ``192.0.2.112``")

2
tox.ini
View File

@ -139,7 +139,7 @@ commands = sphinx-build -W -b html doc/source doc/build/html
# TODO(ihrachys) reenable N537 when new neutron-lib release is available
# N537 Log messages should not be translated
ignore = E125,E126,E128,E129,E265,H404,H405,N530,N534,N536,N537
# H106: Don’t put vim configuration in source files
# H106: Don't put vim configuration in source files
# H203: Use assertIs(Not)None to check for None
# H904: Delay string interpolations at logging calls
enable-extensions=H106,H203,H904