@@ -34,8 +34,8 @@ msgstr ""
 #: bugs.rst:11
 msgid ""
 "It can be sometimes faster to fix bugs yourself and contribute patches to "
-"Python as it streamlines the process and involves less people. Learn how to :"
-"ref:`contribute <contributing-to-python>`."
+"Python as it streamlines the process and involves less people. Learn how "
+"to :ref:`contribute <contributing-to-python>`."
 msgstr ""
 "Bazen hataları kendiniz düzeltmek ve değişikliklerinizi Python'a yama "
 "yaparak katkı sağlamak süreci daha az insan dahil olduğu için "
 
@@ -31,7 +31,7 @@ msgstr ""
 #: c-api/abstract.rst:14
 msgid ""
 "It is not possible to use these functions on objects that are not properly "
-"initialized, such as a list object that has been created by :c:func:"
-"`PyList_New`, but whose items have not been set to some non-\\ ``NULL`` "
-"value yet."
+"initialized, such as a list object that has been created "
+"by :c:func:`PyList_New`, but whose items have not been set to some non-\\ "
+"``NULL`` value yet."
 msgstr ""
@@ -41,8 +41,8 @@ msgid ""
 "Python type object *typeobj* (``PyTypeObject*``). Fields not defined by the "
 "Python object header are not initialized. The caller will own the only "
 "reference to the object (i.e. its reference count will be one). The size of "
-"the memory allocation is determined from the :c:member:`~PyTypeObject."
-"tp_basicsize` field of the type object."
+"the memory allocation is determined from "
+"the :c:member:`~PyTypeObject.tp_basicsize` field of the type object."
 msgstr ""
 
 #: c-api/allocation.rst:43
@@ -60,11 +60,11 @@ msgstr ""
 
 #: c-api/allocation.rst:57
 msgid ""
-"Releases memory allocated to an object using :c:macro:`PyObject_New` or :c:"
-"macro:`PyObject_NewVar`.  This is normally called from the :c:member:"
-"`~PyTypeObject.tp_dealloc` handler specified in the object's type.  The "
-"fields of the object should not be accessed after this call as the memory is "
-"no longer a valid Python object."
+"Releases memory allocated to an object using :c:macro:`PyObject_New` "
+"or :c:macro:`PyObject_NewVar`.  This is normally called from "
+"the :c:member:`~PyTypeObject.tp_dealloc` handler specified in the object's "
+"type.  The fields of the object should not be accessed after this call as "
+"the memory is no longer a valid Python object."
 msgstr ""
 
 #: c-api/allocation.rst:66
 
@@ -23,17 +23,17 @@ msgstr ""
 #: c-api/arg.rst:8
 msgid ""
 "These functions are useful when creating your own extensions functions and "
-"methods.  Additional information and examples are available in :ref:"
-"`extending-index`."
+"methods.  Additional information and examples are available "
+"in :ref:`extending-index`."
 msgstr ""
 
 #: c-api/arg.rst:12
 msgid ""
-"The first three of these functions described, :c:func:`PyArg_ParseTuple`, :c:"
-"func:`PyArg_ParseTupleAndKeywords`, and :c:func:`PyArg_Parse`, all use "
-"*format strings* which are used to tell the function about the expected "
-"arguments.  The format strings use the same syntax for each of these "
-"functions."
+"The first three of these functions "
+"described, :c:func:`PyArg_ParseTuple`, :c:func:`PyArg_ParseTupleAndKeywords`, "
+"and :c:func:`PyArg_Parse`, all use *format strings* which are used to tell "
+"the function about the expected arguments.  The format strings use the same "
+"syntax for each of these functions."
 msgstr ""
 
 #: c-api/arg.rst:19
@@ -98,10 +98,10 @@ msgstr ""
 
 #: c-api/arg.rst:61
 msgid ""
-"To ensure that the underlying buffer may be safely borrowed, the object's :c:"
-"member:`PyBufferProcs.bf_releasebuffer` field must be ``NULL``. This "
-"disallows common mutable objects such as :class:`bytearray`, but also some "
-"read-only objects such as :class:`memoryview` of :class:`bytes`."
+"To ensure that the underlying buffer may be safely borrowed, the "
+"object's :c:member:`PyBufferProcs.bf_releasebuffer` field must be ``NULL``. "
+"This disallows common mutable objects such as :class:`bytearray`, but also "
+"some read-only objects such as :class:`memoryview` of :class:`bytes`."
 msgstr ""
 
 #: c-api/arg.rst:67
@@ -113,11 +113,11 @@ msgstr ""
 
 #: c-api/arg.rst:73
 msgid ""
-"For all ``#`` variants of formats (``s#``, ``y#``, etc.), the macro :c:macro:"
-"`PY_SSIZE_T_CLEAN` must be defined before including :file:`Python.h`. On "
-"Python 3.9 and older, the type of the length argument is :c:type:"
-"`Py_ssize_t` if the :c:macro:`PY_SSIZE_T_CLEAN` macro is defined, or int "
-"otherwise."
+"For all ``#`` variants of formats (``s#``, ``y#``, etc.), the "
+"macro :c:macro:`PY_SSIZE_T_CLEAN` must be defined before "
+"including :file:`Python.h`. On Python 3.9 and older, the type of the length "
+"argument is :c:type:`Py_ssize_t` if the :c:macro:`PY_SSIZE_T_CLEAN` macro is "
+"defined, or int otherwise."
 msgstr ""
 
 #: c-api/arg.rst:80
@@ -138,8 +138,8 @@ msgstr ""
 msgid ""
 "This format does not accept :term:`bytes-like objects <bytes-like object>`.  "
 "If you want to accept filesystem paths and convert them to C character "
-"strings, it is preferable to use the ``O&`` format with :c:func:"
-"`PyUnicode_FSConverter` as *converter*."
+"strings, it is preferable to use the ``O&`` format "
+"with :c:func:`PyUnicode_FSConverter` as *converter*."
 msgstr ""
 
 #: c-api/arg.rst:96
@@ -162,8 +162,8 @@ msgstr ""
 
 #: c-api/arg.rst:106
 msgid ""
-"``s#`` (:class:`str`, read-only :term:`bytes-like object`) [const char \\*, :"
-"c:type:`Py_ssize_t`]"
+"``s#`` (:class:`str`, read-only :term:`bytes-like object`) [const char "
+"\\*, :c:type:`Py_ssize_t`]"
 msgstr ""
 
 #: c-api/arg.rst:107
@@ -238,8 +238,8 @@ msgstr ""
 
 #: c-api/arg.rst:141
 msgid ""
-"``y#`` (read-only :term:`bytes-like object`) [const char \\*, :c:type:"
-"`Py_ssize_t`]"
+"``y#`` (read-only :term:`bytes-like object`) [const char "
+"\\*, :c:type:`Py_ssize_t`]"
 msgstr ""
 
 #: c-api/arg.rst:142
@@ -266,9 +266,9 @@ msgstr ""
 #: c-api/arg.rst:151
 msgid ""
 "Requires that the Python object is a :class:`bytearray` object, without "
-"attempting any conversion.  Raises :exc:`TypeError` if the object is not a :"
-"class:`bytearray` object. The C variable may also be declared as :c:expr:"
-"`PyObject*`."
+"attempting any conversion.  Raises :exc:`TypeError` if the object is not "
+"a :class:`bytearray` object. The C variable may also be declared "
+"as :c:expr:`PyObject*`."
 msgstr ""
 
 #: c-api/arg.rst:155
@@ -290,8 +290,8 @@ msgstr ""
 msgid ""
 "This format accepts any object which implements the read-write buffer "
 "interface. It fills a :c:type:`Py_buffer` structure provided by the caller. "
-"The buffer may contain embedded null bytes. The caller have to call :c:func:"
-"`PyBuffer_Release` when it is done with the buffer."
+"The buffer may contain embedded null bytes. The caller have to "
+"call :c:func:`PyBuffer_Release` when it is done with the buffer."
 msgstr ""
 
 #: c-api/arg.rst:166
@@ -319,8 +319,8 @@ msgstr ""
 msgid ""
 ":c:func:`PyArg_ParseTuple` will allocate a buffer of the needed size, copy "
 "the encoded data into this buffer and adjust *\\*buffer* to reference the "
-"newly allocated storage.  The caller is responsible for calling :c:func:"
-"`PyMem_Free` to free the allocated buffer after use."
+"newly allocated storage.  The caller is responsible for "
+"calling :c:func:`PyMem_Free` to free the allocated buffer after use."
 msgstr ""
 
 #: c-api/arg.rst:183
@@ -338,8 +338,8 @@ msgstr ""
 
 #: c-api/arg.rst:188
 msgid ""
-"``es#`` (:class:`str`) [const char \\*encoding, char \\*\\*buffer, :c:type:"
-"`Py_ssize_t` \\*buffer_length]"
+"``es#`` (:class:`str`) [const char \\*encoding, char "
+"\\*\\*buffer, :c:type:`Py_ssize_t` \\*buffer_length]"
 msgstr ""
 
 #: c-api/arg.rst:189
@@ -419,8 +419,8 @@ msgstr ""
 
 #: c-api/arg.rst:233
 msgid ""
-"Convert a nonnegative Python integer to an unsigned tiny int, stored in a C :"
-"c:expr:`unsigned char`."
+"Convert a nonnegative Python integer to an unsigned tiny int, stored in a "
+"C :c:expr:`unsigned char`."
 msgstr ""
 
 #: c-api/arg.rst:580
@@ -572,9 +572,9 @@ msgstr ""
 #: c-api/arg.rst:295
 msgid ""
 "Store a Python object (without any conversion) in a C object pointer.  The C "
-"program thus receives the actual object that was passed.  A new :term:"
-"`strong reference` to the object is not created (i.e. its reference count is "
-"not increased). The pointer stored is not ``NULL``."
+"program thus receives the actual object that was passed.  A "
+"new :term:`strong reference` to the object is not created (i.e. its "
+"reference count is not increased). The pointer stored is not ``NULL``."
 msgstr ""
 
 #: c-api/arg.rst:301
@@ -608,12 +608,12 @@ msgstr ""
 
 #: c-api/arg.rst:318
 msgid ""
-"where *object* is the Python object to be converted and *address* is the :c:"
-"expr:`void*` argument that was passed to the ``PyArg_Parse*`` function. The "
-"returned *status* should be ``1`` for a successful conversion and ``0`` if "
-"the conversion has failed.  When the conversion fails, the *converter* "
-"function should raise an exception and leave the content of *address* "
-"unmodified."
+"where *object* is the Python object to be converted and *address* is "
+"the :c:expr:`void*` argument that was passed to the ``PyArg_Parse*`` "
+"function. The returned *status* should be ``1`` for a successful conversion "
+"and ``0`` if the conversion has failed.  When the conversion fails, the "
+"*converter* function should raise an exception and leave the content of "
+"*address* unmodified."
 msgstr ""
 
 #: c-api/arg.rst:324
@@ -711,8 +711,8 @@ msgstr ""
 #: c-api/arg.rst:378
 msgid ""
 "The list of format units ends here; the string after the semicolon is used "
-"as the error message *instead* of the default error message.  ``:`` and ``;"
-"`` mutually exclude each other."
+"as the error message *instead* of the default error message.  ``:`` and "
+"``;`` mutually exclude each other."
 msgstr ""
 
 #: c-api/arg.rst:382
@@ -763,9 +763,10 @@ msgstr ""
 msgid ""
 "Parse the parameters of a function that takes both positional and keyword "
 "parameters into local variables.  The *keywords* argument is a ``NULL``-"
-"terminated array of keyword parameter names.  Empty names denote :ref:"
-"`positional-only parameters <positional-only_parameter>`. Returns true on "
-"success; on failure, it returns false and raises the appropriate exception."
+"terminated array of keyword parameter names.  Empty names "
+"denote :ref:`positional-only parameters <positional-only_parameter>`. "
+"Returns true on success; on failure, it returns false and raises the "
+"appropriate exception."
 msgstr ""
 
 #: c-api/arg.rst:425
@@ -874,10 +875,10 @@ msgid ""
 "When memory buffers are passed as parameters to supply data to build "
 "objects, as for the ``s`` and ``s#`` formats, the required data is copied.  "
 "Buffers provided by the caller are never referenced by the objects created "
-"by :c:func:`Py_BuildValue`.  In other words, if your code invokes :c:func:"
-"`malloc` and passes the allocated memory to :c:func:`Py_BuildValue`, your "
-"code is responsible for calling :c:func:`free` for that memory once :c:func:"
-"`Py_BuildValue` returns."
+"by :c:func:`Py_BuildValue`.  In other words, if your code "
+"invokes :c:func:`malloc` and passes the allocated memory "
+"to :c:func:`Py_BuildValue`, your code is responsible for "
+"calling :c:func:`free` for that memory once :c:func:`Py_BuildValue` returns."
 msgstr ""
 
 #: c-api/arg.rst:521
@@ -1066,9 +1067,9 @@ msgid ""
 "Pass a Python object untouched but create a new :term:`strong reference` to "
 "it (i.e. its reference count is incremented by one). If the object passed in "
 "is a ``NULL`` pointer, it is assumed that this was caused because the call "
-"producing the argument found an error and set an exception. Therefore, :c:"
-"func:`Py_BuildValue` will return ``NULL`` but won't raise an exception.  If "
-"no exception has been raised yet, :exc:`SystemError` is set."
+"producing the argument found an error and set an exception. "
+"Therefore, :c:func:`Py_BuildValue` will return ``NULL`` but won't raise an "
+"exception.  If no exception has been raised yet, :exc:`SystemError` is set."
 msgstr ""
 
 #: c-api/arg.rst:628
@@ -1093,9 +1094,9 @@ msgstr ""
 #: c-api/arg.rst:637
 msgid ""
 "Convert *anything* to a Python object through a *converter* function.  The "
-"function is called with *anything* (which should be compatible with :c:expr:"
-"`void*`) as its argument and should return a \"new\" Python object, or "
-"``NULL`` if an error occurred."
+"function is called with *anything* (which should be compatible "
+"with :c:expr:`void*`) as its argument and should return a \"new\" Python "
+"object, or ``NULL`` if an error occurred."
 msgstr ""
 
 #: c-api/arg.rst:643