Skip to content

Commit

Permalink
docs(storage): few spelling fixes for generate_signed_url() (#85)
Browse files Browse the repository at this point in the history
  • Loading branch information
Gurov Ilya committed Mar 13, 2020
1 parent 5adc8b0 commit 635951a
Showing 1 changed file with 6 additions and 7 deletions.
13 changes: 6 additions & 7 deletions google/cloud/storage/blob.py
Expand Up @@ -438,23 +438,22 @@ def generate_signed_url(
:type headers: dict
:param headers:
(Optional) Additional HTTP headers to be included as part of the
signed URLs. See:
signed URLs. See:
https://cloud.google.com/storage/docs/xml-api/reference-headers
Requests using the signed URL *must* pass the specified header
(name and value) with each request for the URL.
:type query_parameters: dict
:param query_parameters:
(Optional) Additional query paramtersto be included as part of the
signed URLs. See:
(Optional) Additional query parameters to be included as part of the
signed URLs. See:
https://cloud.google.com/storage/docs/xml-api/reference-headers#query
:type client: :class:`~google.cloud.storage.client.Client` or
``NoneType``
:param client: (Optional) The client to use. If not passed, falls back
:param client: (Optional) The client to use. If not passed, falls back
to the ``client`` stored on the blob's bucket.
:type credentials: :class:`google.auth.credentials.Credentials` or
:class:`NoneType`
:param credentials: The authorization credentials to attach to requests.
Expand All @@ -479,8 +478,8 @@ def generate_signed_url(
:type bucket_bound_hostname: str
:param bucket_bound_hostname:
(Optional) If pass, then construct the URL relative to the bucket-bound hostname.
Value cane be a bare or with scheme, e.g., 'example.com' or 'http://example.com'.
(Optional) If passed, then construct the URL relative to the bucket-bound hostname.
Value can be a bare or with scheme, e.g., 'example.com' or 'http://example.com'.
See: https://cloud.google.com/storage/docs/request-endpoints#cname
:type scheme: str
Expand Down

0 comments on commit 635951a

Please sign in to comment.