Skip to content

Commit e30afb0

Browse files
lcl1024ryjones
authored andcommitted
[zh-CN]Fix duplicate content in zh_CN/source/policies.rst to match other languages
Signed-off-by: softtr <[email protected]>
1 parent 681fd4f commit e30afb0

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

docs/locale/zh_CN/source/policies.rst

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -210,27 +210,21 @@ component resembling a file basename is the policy name.
210210
Writers
211211
Admins
212212

213-
Different components of the system will refer to these policy names. For
214-
instance, to call ``Deliver`` on the orderer, the signature on the
215-
request must satisfy the ``/Channel/Readers`` policy. However, to gossip
216-
a block to a peer will require that the ``/Channel/Application/Readers``
217-
policy be satisfied.
218-
219213
Consider the Writers policy referred to with the ``------->`` mark in
220214
the above example. This policy may be referred to by the shorthand
221215
notation ``/Channel/Application/Writers``. Note that the elements
222216
resembling directory components are group names, while the last
223217
component resembling a file basename is the policy name.
224218

225-
By setting these different policies, the system can be configured with
226-
rich access controls.
227-
228219
Different components of the system will refer to these policy names. For
229220
instance, to call ``Deliver`` on the orderer, the signature on the
230221
request must satisfy the ``/Channel/Readers`` policy. However, to gossip
231222
a block to a peer will require that the ``/Channel/Application/Readers``
232223
policy be satisfied.
233224

225+
By setting these different policies, the system can be configured with
226+
rich access controls.
227+
234228
Constructing a SignaturePolicy
235229
------------------------------
236230

0 commit comments

Comments
 (0)