From 7eb081842dc09e19438c953cdcecd2eda78c736d Mon Sep 17 00:00:00 2001 From: Ikko Ashimine Date: Tue, 26 Jul 2022 17:28:31 +0900 Subject: [PATCH] PEP 694: Fix typos (#2731) Co-authored-by: CAM Gerlach --- pep-0694.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pep-0694.rst b/pep-0694.rst index e1a6dc38c..1f5471222 100644 --- a/pep-0694.rst +++ b/pep-0694.rst @@ -92,7 +92,7 @@ Encoding 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 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 @@ -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 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 @@ -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. -Session Cancelation -~~~~~~~~~~~~~~~~~~~ +Session Cancellation +~~~~~~~~~~~~~~~~~~~~ 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 @@ -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. 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. @@ -559,7 +559,7 @@ the ``application/octet-stream`` content-type. 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 serialization formats, which includes the ``format`` url parameter.