qapi: fix typos in documentation JSON examples

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
This commit is contained in:
Stefan Hajnoczi 2011-10-28 15:58:26 +01:00
parent d0bc5bc3aa
commit acf8394eae
1 changed files with 2 additions and 2 deletions

View File

@ -41,7 +41,7 @@ dictionary. This corresponds to a struct in C or an Object in JSON. An
example of a complex type is: example of a complex type is:
{ 'type': 'MyType', { 'type': 'MyType',
'data' { 'member1': 'str', 'member2': 'int', '*member3': 'str } } 'data': { 'member1': 'str', 'member2': 'int', '*member3': 'str' } }
The use of '*' as a prefix to the name means the member is optional. Optional The use of '*' as a prefix to the name means the member is optional. Optional
members should always be added to the end of the dictionary to preserve members should always be added to the end of the dictionary to preserve
@ -63,7 +63,7 @@ An example command is:
{ 'command': 'my-command', { 'command': 'my-command',
'data': { 'arg1': 'str', '*arg2': 'str' }, 'data': { 'arg1': 'str', '*arg2': 'str' },
'returns': 'str' ] 'returns': 'str' }
Command names should be all lower case with words separated by a hyphen. Command names should be all lower case with words separated by a hyphen.