From 3f8ec46be84dd10ffbba52e4d0551147e5901db9 Mon Sep 17 00:00:00 2001 From: liumk Date: Fri, 9 Feb 2018 04:16:30 -0500 Subject: [PATCH] fix somes typos in doc file. Change-Id: I5a27ddb6fcbcaa21c223d0b76e733063acce4556 --- doc/source/firehose.rst | 2 +- doc/source/firehose_schema.rst | 4 ++-- doc/source/third_party.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/source/firehose.rst b/doc/source/firehose.rst index d705907334..c6184bcbc7 100644 --- a/doc/source/firehose.rst +++ b/doc/source/firehose.rst @@ -274,7 +274,7 @@ on the firehose and print it to STDOUT Using SSL/TLS ------------- If you would like to connect to the firehose using ssl to encrypt the events you -recieve from MQTT you just need to connect with ssl enabled via either of the +receive from MQTT you just need to connect with ssl enabled via either of the encrypted ports. If you'd like to verify the server ssl certificate when connecting you'll need to provide a CA bundle to use as most MQTT clients do not know how to use the system trusted CA bundle like most http clients. diff --git a/doc/source/firehose_schema.rst b/doc/source/firehose_schema.rst index 3d05470d93..11e5544b8e 100644 --- a/doc/source/firehose_schema.rst +++ b/doc/source/firehose_schema.rst @@ -85,7 +85,7 @@ Payload ------- The payload of messages is dynamically generated and dependent on the -notification recieved from launchpad, and launchpad isn't always consistent in +notification received from launchpad, and launchpad isn't always consistent in what fields are present in those notifications. However, for bug event types there is a standard format. The fields which @@ -181,7 +181,7 @@ that the event is for, this is either going to be ``start`` or ``finish``. * ``OK`` * ``FAILED`` -to indicate whether the playbook succesfully executed or not. +to indicate whether the playbook successfully executed or not. Playbook Stats Events ''''''''''''''''''''' diff --git a/doc/source/third_party.rst b/doc/source/third_party.rst index 9100283338..01398ed9ed 100644 --- a/doc/source/third_party.rst +++ b/doc/source/third_party.rst @@ -422,7 +422,7 @@ this list that your account has been disabled will include instructions for getting your system re-enabled. You are also welcome to join us in the #openstack-infra irc channel on freenode to discuss your situation. -In order to get your Third Pary CI account to have voting permissions on +In order to get your Third Party CI account to have voting permissions on repos in gerrit in addition to ``openstack-dev/ci-sandbox`` you have a greater chance of success if you follow these steps: