diff --git a/doc/source/deploy/install-guide.rst b/doc/source/deploy/install-guide.rst index bbf8417865..0a3f109b8c 100644 --- a/doc/source/deploy/install-guide.rst +++ b/doc/source/deploy/install-guide.rst @@ -890,8 +890,8 @@ controller in your bare metal server by using ``ipmitool``:: *Note:* -#. This is not the bare metal server’s main IP. The IPMI controller - should have it’s own unique IP. +#. This is not the bare metal server's main IP. The IPMI controller + should have it's own unique IP. #. In case the above command doesn't return the power status of the bare metal server, check for these: diff --git a/doc/source/deploy/upgrade-guide.rst b/doc/source/deploy/upgrade-guide.rst index e2001a5c84..0e72adbc77 100644 --- a/doc/source/deploy/upgrade-guide.rst +++ b/doc/source/deploy/upgrade-guide.rst @@ -27,7 +27,7 @@ your Nova and Ironic services are as follows: - Install new python-ironicclient code. - Restart Nova services. - Install new Ironic code, run database migrations, restart Ironic services. -- Edit nova.conf and set force_config_drive to your liking, restaring +- Edit nova.conf and set force_config_drive to your liking, restarting nova-compute if necessary. Note that during the period between Nova's upgrade and Ironic's upgrades, diff --git a/doc/source/dev/dev-quickstart.rst b/doc/source/dev/dev-quickstart.rst index 1ae9b552bd..fc3d8fcc31 100644 --- a/doc/source/dev/dev-quickstart.rst +++ b/doc/source/dev/dev-quickstart.rst @@ -22,8 +22,8 @@ Install prerequisites: sudo yum install python-devel openssl-devel python-pip mysql-devel libxml2-devel libxslt-devel postgresql-devel git git-review libffi-devel gettext ipmitool psmisc graphviz - If using RHEL and yum reports “No package python-pip available” and “No - package git-review available”, use the EPEL software repository. + If using RHEL and yum reports "No package python-pip available" and "No + package git-review available", use the EPEL software repository. Instructions can be found at ``_. - openSUSE/SLE 12:: diff --git a/doc/source/dev/drivers.rst b/doc/source/dev/drivers.rst index eb9e640c29..01216a44a5 100644 --- a/doc/source/dev/drivers.rst +++ b/doc/source/dev/drivers.rst @@ -57,12 +57,12 @@ While performing the request, a lock is held on the node, and other requests for the node will be delayed and may fail with an HTTP 409 (Conflict) error code. -This endpoint exposes a node’s driver directly, and as such, it is -expressly not part of Ironic’s standard REST API. There is only a +This endpoint exposes a node's driver directly, and as such, it is +expressly not part of Ironic's standard REST API. There is only a single HTTP endpoint exposed, and the semantics of the message body are determined solely by the driver. Ironic makes no guarantees about backwards compatibility; this is solely up to the discretion of each -driver’s author. +driver's author. To get information about all the methods available via the vendor_passthru endpoint for a particular node, you can issue an HTTP GET request:: @@ -70,8 +70,8 @@ endpoint for a particular node, you can issue an HTTP GET request:: GET /v1/nodes//vendor_passthru/methods The response's JSON body will contain information for each method, -such as the method’s name, a description, the HTTP methods supported, -and whether it’s asynchronous or synchronous. +such as the method's name, a description, the HTTP methods supported, +and whether it's asynchronous or synchronous. Driver Vendor Passthru @@ -100,7 +100,7 @@ A method: HTTP 409 (Conflict) error code. Ironic makes no guarantees about the semantics of the message BODY sent -to this endpoint. That is left up to each driver’s author. +to this endpoint. That is left up to each driver's author. To get information about all the methods available via the driver vendor_passthru endpoint, you can issue an HTTP GET request:: @@ -108,5 +108,5 @@ vendor_passthru endpoint, you can issue an HTTP GET request:: GET /v1/drivers//vendor_passthru/methods The response's JSON body will contain information for each method, -such as the method’s name, a description, the HTTP methods supported, -and whether it’s asynchronous or synchronous. +such as the method's name, a description, the HTTP methods supported, +and whether it's asynchronous or synchronous.