openstack/security-doc
Code Issues Proposed changes

Use double backticks for command options

Browse Source 
Sphinx 1.5 warns about :option: usage without .. option:: description.
Since we do not use .. option:: to describe parameter, remove
:option: from the tools.

Change-Id: I7215aafe4c2f32e2ebc255343f862eea3f49e3be
This commit is contained in:
KATO Tomoyuki
2017-01-14 18:52:51 +09:00
parent 80ba2dec91
commit 911a2547ae
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
security-guide/source/shared-file-systems/share-acl.rst
View File

@@ -12,7 +12,7 @@ access to a specified share, and list permissions for a specified share.
A share can be *public* or *private*. This is a level of visibility for the
share that defines whether other tenants can or cannot see the share. By
default, all shares are created as private. While creating a share, use key
:option:`--public` to make your share public for other tenants to see it in a
``--public`` to make your share public for other tenants to see it in a
list of shares and see its detailed information.
According to a :ref:`policy.json <shared_fs_policies>` file, an administrator

2
security-guide/source/shared-file-systems/share-type-acl.rst
View File

@@ -22,7 +22,7 @@ visibility for the share type that defines whether other tenants can or cannot
see it in a share types list and use it to create a new share.
By default, share types are created as public. While creating a share type,
use :option:`--is_public` parameter set to ``False`` to make your share type
use ``--is_public`` parameter set to ``False`` to make your share type
private which will prevent other tenants from seeing it in a list of share
types and creating new shares with it. On the other hand, *public* share
types are available to every tenant in a cloud.