Skip to content

Commit fc65918

Browse files
committed
Fix some links and lints
1 parent 70b1bf7 commit fc65918

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

peps/pep-0694.rst

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -793,7 +793,7 @@ The structure of the ``Content-Type`` header for all other requests is:
793793
Since minor API version differences should never be disruptive, only the major version is included
794794
in the content type; the version number is prefixed with a ``v``.
795795

796-
Unlike :pep:`691`, this PEP does not change the existing *legacy* `1.0`` upload API in any way, so
796+
Unlike :pep:`691`, this PEP does not change the existing *legacy* ``1.0`` upload API in any way, so
797797
servers are required to host the new API described in this PEP at a different endpoint than the
798798
existing upload API.
799799

@@ -834,7 +834,7 @@ Is this Resumable Upload protocol based on anything?
834834

835835
Yes!
836836

837-
It's actually the protocol specified in an `Active Internet-Draft <ietf-draft>`_, where the authors
837+
It's actually the protocol specified in an `active internet draft <ietf-draft>`_, where the authors
838838
took what they learned implementing `tus <https://tus.io/>`_ to provide the idea of resumable
839839
uploads in a wholly generic, standards based way.
840840

@@ -883,8 +883,8 @@ Open Questions
883883
Multipart Uploads vs tus
884884
------------------------
885885

886-
This PEP currently bases the actual uploading of files on an internet draft from ``tus.io`` that
887-
supports resumable file uploads.
886+
This PEP currently bases the actual uploading of files on an `internet draft <ietf-draft>`_
887+
(originally designed by `tus.io <https://tus.io/>`__) that supports resumable file uploads.
888888

889889
That protocol requires a few things:
890890

@@ -983,8 +983,8 @@ erase most of the server side implementation simplification.
983983
.. [#fn-chunk-token] Single request uploads **MAY** include the ``Upload-Token`` header, but it is
984984
not required in that case.
985985
986-
.. [#fn-immutable] Published files may still be `yanked <https://peps.python.org/pep-0592/>`__ or
987-
`deleted <https://pypi.org/help/#file-name-reuse>`__ as normal.
986+
.. [#fn-immutable] Published files may still be yanked (i.e. :pep:`592`) or `deleted
987+
<https://pypi.org/help/#file-name-reuse>`__ as normal.
988988
989989
990990
Copyright

0 commit comments

Comments
 (0)