Update peps/pep-0795.rst

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: TobiasWrigstad

peps/pep-0795.rst

@@ -47,33 +47,6 @@ to decide if it wants to provide immutability or not. We have a
 working implementation of this PEP for CPython which we aim to adjust
 based on feedback and upstream on acceptance.
 
-Changes from the previous draft
-===============================
-
-This PEP is a complete rewrite of the original PEP after `discussions on
-DPO`_ and elsewhere. Based on feedback from DPO this rewrite:
-
-.. _discussions on DPO: https://discuss.python.org/t/pep-795-add-deep-immutability-to-python/96014
-
--  Focuses more on programming model, not just implementation details
--  Aims to be clearer about what the costs are for different parts of
-   the design, both in terms of complexity for programmers and
-   implementers of this PEP
--  Aims to make the semantics of freezing clearer, and provide more
-   examples of how freezing propagates
--  Adds a new design that provides control over freeze propagation
--  Adds escape hatches and clearly points out who implements them
--  Motivates the design by linking it clearer to sharing objects across
-   sub-interpreters
--  Aims to be clearer about the semantics of immutable functions (and why
-   they are unavoidable)
--  Discusses the role of types and future plans for types
--  Includes direct sharing of immutable objects across sub-interpreters,
-   rather than making a separate PEP for this
--  Removes a lot of the rejected alternatives from the original PEP;
-   this is motivated by this PEP already being very long, and because
-   the inclusion of direct sharing across sub-interpreters motivate many
-   of the design decisions