Skip to content

Commit b68e488

Browse files
docs: [google-cloud-parallelstore] fix various typos in commentary (#13957)
BEGIN_COMMIT_OVERRIDE docs: fix various typos in commentary END_COMMIT_OVERRIDE - [ ] Regenerate this pull request now. PiperOrigin-RevId: 764977880 Source-Link: googleapis/googleapis@021fc2e Source-Link: googleapis/googleapis-gen@9fb7f64 Copy-Tag: eyJwIjoicGFja2FnZXMvZ29vZ2xlLWNsb3VkLXBhcmFsbGVsc3RvcmUvLk93bEJvdC55YW1sIiwiaCI6IjlmYjdmNjRmODE2ODZjNjcyY2Y3M2I5MmJkNTQyNjNjOTU1OWNlMTgifQ== --------- Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
1 parent f49ee52 commit b68e488

File tree

1 file changed

+30
-30
lines changed
  • packages/google-cloud-parallelstore/google/cloud/parallelstore_v1beta/types

1 file changed

+30
-30
lines changed

packages/google-cloud-parallelstore/google/cloud/parallelstore_v1beta/types/parallelstore.py

Lines changed: 30 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -161,8 +161,8 @@ class Instance(proto.Message):
161161
between 12000 and 100000, in multiples of 4000;
162162
e.g., 12000, 16000, 20000, ...
163163
daos_version (str):
164-
Output only. Deprecated 'daos_version' field. Output only.
165-
The version of DAOS software running in the instance.
164+
Output only. Deprecated: The version of DAOS
165+
software running in the instance.
166166
access_points (MutableSequence[str]):
167167
Output only. A list of IPv4 addresses used
168168
for client side configuration.
@@ -320,7 +320,7 @@ class TransferMetadataOptions(proto.Message):
320320
"""
321321

322322
class Uid(proto.Enum):
323-
r"""The UID perservation behavior.
323+
r"""The UID preservation behavior.
324324
325325
Values:
326326
UID_UNSPECIFIED (0):
@@ -506,11 +506,11 @@ class CreateInstanceRequest(proto.Message):
506506
for at least 60 minutes since the first request.
507507
508508
For example, consider a situation where you make
509-
an initial request and t he request times out.
510-
If you make the request again with the same
511-
request ID, the server can check if original
512-
operation with the same request ID was received,
513-
and if so, will ignore the second request. This
509+
an initial request and the request times out. If
510+
you make the request again with the same request
511+
ID, the server can check if original operation
512+
with the same request ID was received, and if
513+
so, will ignore the second request. This
514514
prevents clients from accidentally creating
515515
duplicate commitments.
516516
@@ -559,11 +559,11 @@ class UpdateInstanceRequest(proto.Message):
559559
for at least 60 minutes since the first request.
560560
561561
For example, consider a situation where you make
562-
an initial request and t he request times out.
563-
If you make the request again with the same
564-
request ID, the server can check if original
565-
operation with the same request ID was received,
566-
and if so, will ignore the second request. This
562+
an initial request and the request times out. If
563+
you make the request again with the same request
564+
ID, the server can check if original operation
565+
with the same request ID was received, and if
566+
so, will ignore the second request. This
567567
prevents clients from accidentally creating
568568
duplicate commitments.
569569
@@ -603,11 +603,11 @@ class DeleteInstanceRequest(proto.Message):
603603
for at least 60 minutes after the first request.
604604
605605
For example, consider a situation where you make
606-
an initial request and t he request times out.
607-
If you make the request again with the same
608-
request ID, the server can check if original
609-
operation with the same request ID was received,
610-
and if so, will ignore the second request. This
606+
an initial request and the request times out. If
607+
you make the request again with the same request
608+
ID, the server can check if original operation
609+
with the same request ID was received, and if
610+
so, will ignore the second request. This
611611
prevents clients from accidentally creating
612612
duplicate commitments.
613613
@@ -777,11 +777,11 @@ class ImportDataRequest(proto.Message):
777777
for at least 60 minutes since the first request.
778778
779779
For example, consider a situation where you make
780-
an initial request and t he request times out.
781-
If you make the request again with the same
782-
request ID, the server can check if original
783-
operation with the same request ID was received,
784-
and if so, will ignore the second request. This
780+
an initial request and the request times out. If
781+
you make the request again with the same request
782+
ID, the server can check if original operation
783+
with the same request ID was received, and if
784+
so, will ignore the second request. This
785785
prevents clients from accidentally creating
786786
duplicate commitments.
787787
@@ -861,11 +861,11 @@ class ExportDataRequest(proto.Message):
861861
for at least 60 minutes since the first request.
862862
863863
For example, consider a situation where you make
864-
an initial request and t he request times out.
865-
If you make the request again with the same
866-
request ID, the server can check if original
867-
operation with the same request ID was received,
868-
and if so, will ignore the second request. This
864+
an initial request and the request times out. If
865+
you make the request again with the same request
866+
ID, the server can check if original operation
867+
with the same request ID was received, and if
868+
so, will ignore the second request. This
869869
prevents clients from accidentally creating
870870
duplicate commitments.
871871
@@ -1230,10 +1230,10 @@ class TransferCounters(proto.Message):
12301230
Bytes that are copied to the data
12311231
destination.
12321232
objects_failed (int):
1233-
Objects that are failed to write to the data
1233+
Objects that failed to be written to the data
12341234
destination.
12351235
bytes_failed (int):
1236-
Bytes that are failed to write to the data
1236+
Bytes that failed to be written to the data
12371237
destination.
12381238
"""
12391239

0 commit comments

Comments
 (0)