openstack/zaqar
Code Issues Proposed changes

Fix some typos in zaqar

Browse Source 
There are some typos in zaqar, this patch fix it.

Change-Id: Ic174ed786eaaa0542c68f178dee0a730ddc81b55
This commit is contained in:
gecong1973 2017-06-15 20:49:51 -04:00
parent 28f1f0f937
commit 48d6855f5d
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/OSprofiler.rst
View File

@ -84,7 +84,7 @@ Command Line
------------ ------------
we can use OpenStack Client to analyse the user request now. For example, if we we can use OpenStack Client to analyse the user request now. For example, if we
want know the performance for "queue list", we can do like this: want to know the performance for "queue list", we can do like this:
1. OpenStack Client now supports OSprofiler by default. Only thing we need to 1. OpenStack Client now supports OSprofiler by default. Only thing we need to
do is adding ``--os-profile {hmac_keys}`` in the command:: do is adding ``--os-profile {hmac_keys}`` in the command::
@ -112,7 +112,7 @@ It also supports json format::
osprofiler trace show --json 2902c7a3-ee18-4b08-aae7-4e34388f9352 --connection-string mongodb://localhost:27017 osprofiler trace show --json 2902c7a3-ee18-4b08-aae7-4e34388f9352 --connection-string mongodb://localhost:27017
Of cause it supports to save the result to a file:: Of course it supports to save the result to a file::
osprofiler trace show --json 2902c7a3-ee18-4b08-aae7-4e34388f9352 --out list_test --connection-string mongodb://localhost:27017 osprofiler trace show --json 2902c7a3-ee18-4b08-aae7-4e34388f9352 --out list_test --connection-string mongodb://localhost:27017

2
doc/source/glossary.rst
View File

@ -49,7 +49,7 @@ protocol, which is one of the main requirements in today’s scalable applicatio
Producer - Consumer Producer - Consumer
Producer - Consumer is a pattern where each worker application that reads Producer - Consumer is a pattern where each worker application that reads
the queue has to claim the message in order to prevent duplicate processing. the queue has to claim the message in order to prevent duplicate processing.
Later, when the work is done, the worker is responsible from deleting the Later, when the work is done, the worker is responsible for deleting the
message. If message is not deleted in a predefined time (claim TTL), it can message. If message is not deleted in a predefined time (claim TTL), it can
be claimed by other workers. be claimed by other workers.