Skip to content

Commit d97fe57

Browse files
authored
fix(AIP-2510): add bold **should** resource ref (#1112)
The original PR missed the bolding to clarify it follows the RFC-2119 terminology.
1 parent d97fd2e commit d97fe57

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

aip/cloud/2510.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Project identifiers also appear in [resource names][]. These resource
7373
names are used both to identify the resource itself and can refer to
7474
other resources ([example][]).
7575

76-
When project identifiers are provided, the response should
76+
When project identifiers are provided, the response **should**
7777
include the identifier as it occurred in the request: if the project ID
7878
was provided it should be returned, and if the project number was
7979
provided, that is what should be in the response.
@@ -130,10 +130,10 @@ and if the value of `name` on such a request is,
130130
projects/my-project/books/les-miserables
131131
```
132132

133-
then the value of the field, `name`, returned for the `Book`, should match: the
134-
project ID and not the number should be returned. But, the value for the field,
135-
`shelf` should use the project number, as the create request had submitted a
136-
shelf with the project number in the resource name.
133+
then the value of the field, `name`, returned for the `Book`, **should** match:
134+
the project ID and not the number should be returned. But, the value for the
135+
field, `shelf` should use the project number, as the create request had
136+
submitted a shelf with the project number in the resource name.
137137

138138
In other words, the following values should be returned:
139139

0 commit comments

Comments
 (0)