PEP 694: Fix typos (#2731)
Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
This commit is contained in:
parent
fd50a6c9e1
commit
7eb081842d
12
pep-0694.rst
12
pep-0694.rst
|
@ -92,7 +92,7 @@ Encoding
|
||||||
The data to be submitted is submitted as a ``POST`` request with the content type
|
The data to be submitted is submitted as a ``POST`` request with the content type
|
||||||
of ``multipart/form-data``. This is due to the historical nature, that this API
|
of ``multipart/form-data``. This is due to the historical nature, that this API
|
||||||
was not actually designed as an API, but rather was a form on the initial PyPI
|
was not actually designed as an API, but rather was a form on the initial PyPI
|
||||||
implmentation, then client code was written to programatically submit that form.
|
implementation, then client code was written to programmatically submit that form.
|
||||||
|
|
||||||
|
|
||||||
Content
|
Content
|
||||||
|
@ -426,7 +426,7 @@ they need to upload a different file, they may do so by issuing a ``DELETE``
|
||||||
request to the file upload URL with the ``Upload-Token`` used to upload the
|
request to the file upload URL with the ``Upload-Token`` used to upload the
|
||||||
file in the first place.
|
file in the first place.
|
||||||
|
|
||||||
A successful cancelation request **MUST** response with a ``204 No Content``.
|
A successful cancellation request **MUST** response with a ``204 No Content``.
|
||||||
|
|
||||||
|
|
||||||
Delete an uploaded File
|
Delete an uploaded File
|
||||||
|
@ -451,8 +451,8 @@ they got when they initially created the upload session, except with any
|
||||||
changes to ``status``, ``valid-for``, or updated ``files`` reflected.
|
changes to ``status``, ``valid-for``, or updated ``files`` reflected.
|
||||||
|
|
||||||
|
|
||||||
Session Cancelation
|
Session Cancellation
|
||||||
~~~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~~~~
|
||||||
|
|
||||||
To cancel an upload session, a client issues a ``DELETE`` request to the
|
To cancel an upload session, a client issues a ``DELETE`` request to the
|
||||||
same session URL as before. At which point the server marks the session as
|
same session URL as before. At which point the server marks the session as
|
||||||
|
@ -515,7 +515,7 @@ a ``source`` key, which is a string that indicates what the source of the
|
||||||
error is, and a ``messasge`` key for that specific error.
|
error is, and a ``messasge`` key for that specific error.
|
||||||
|
|
||||||
The ``message`` and ``source`` strings do not have any specific meaning, and
|
The ``message`` and ``source`` strings do not have any specific meaning, and
|
||||||
are intended for human interpetation to figure out what the underlying issue
|
are intended for human interpretation to figure out what the underlying issue
|
||||||
was.
|
was.
|
||||||
|
|
||||||
|
|
||||||
|
@ -559,7 +559,7 @@ the ``application/octet-stream`` content-type.
|
||||||
Version + Format Selection
|
Version + Format Selection
|
||||||
--------------------------
|
--------------------------
|
||||||
|
|
||||||
Again similiar to :pep:`691`, this PEP standardizes on using server-driven
|
Again similar to :pep:`691`, this PEP standardizes on using server-driven
|
||||||
content negotiation to allow clients to request different versions or
|
content negotiation to allow clients to request different versions or
|
||||||
serialization formats, which includes the ``format`` url parameter.
|
serialization formats, which includes the ``format`` url parameter.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue