Simplify relative paths text

Signed-off-by: Filipe Laíns <lains@riseup.net>

Author: FFY00

peps/pep-0739.rst

@@ -132,7 +132,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - Base prefix of the Python installation.
 
-        Either an absolute path, or a relative path to directory where
+        Either an absolute path, or a path relative to directory where
         this file is contained.
     * - Examples
       - ``/usr``, ``../..``, etc.
@@ -150,8 +150,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - The path to the Python interprer of the base installation.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
 
         This field **MUST** be present if the installation provides an
         interpreter executable.
@@ -531,8 +530,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - The path to the dynamic ``libpython`` library.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
 
         This field **MUST** be present if the Python installation
         provides a dynamic ``libpython`` library, otherwise this entry
@@ -556,8 +554,7 @@ below, which is rendered in an human-readable format here.
       - The path to the dynamic ``libpython`` library for the stable
         ABI.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
 
         This field **MUST** be present if the Python installation
         provides a dynamic ``libpython`` library targetting the Stable
@@ -582,8 +579,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - The path to the static ``libpython`` library.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
 
         This field **MUST** be present if the Python installation
         provides a static ``libpython`` library, otherwise this entry
@@ -642,8 +638,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - The path to the C API headers.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
     * - Examples
       - - ``/usr/include/python3.14``
         - ``include/python3.14``
@@ -662,8 +657,7 @@ below, which is rendered in an human-readable format here.
     * - Description
       - The path to the pkg-config definition files.
 
-        Either an absolute path, or a relative path to the path defined
-        in the ``base_prefix`` key.
+        Either an absolute path, or a path relative to ``base_prefix``.
 
         This field **MUST** be present if the Python implementation
         provides pkg-config definition files, otherwise this section

peps/pep-0739/python-build-info-v1.0.schema.json

@@ -19,15 +19,15 @@
     },
     "base_prefix": {
       "type": "string",
-      "description": "Base prefix of the Python installation.\n\nEither an absolute path, or a relative path to directory where this file is contained.",
+      "description": "Base prefix of the Python installation.\n\nEither an absolute path, or a path relative to directory where this file is contained.",
       "examples": [
         "/usr",
         "../.."
       ]
     },
     "base_interpreter": {
         "type": "string",
-        "description": "The path to the Python interprer of the base installation.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.\n\nThis field **MUST** be present if the installation provides an interpreter executable.",
+        "description": "The path to the Python interprer of the base installation.\n\nEither an absolute path, or a path relative to ``base_prefix``.\n\nThis field **MUST** be present if the installation provides an interpreter executable.",
         "examples": [
           "/usr/bin/python",
           "bin/python"
@@ -199,23 +199,23 @@
       "properties": {
         "dynamic": {
           "type": "string",
-          "description": "The path to the dynamic ``libpython`` library.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.\n\nThis field **MUST** be present if the Python installation provides a dynamic ``libpython`` library, otherwise this entry will be missing.",
+          "description": "The path to the dynamic ``libpython`` library.\n\nEither an absolute path, or a path relative to ``base_prefix``.\n\nThis field **MUST** be present if the Python installation provides a dynamic ``libpython`` library, otherwise this entry will be missing.",
           "examples": [
             "/usr/lib/libpython3.14.so.1.0",
             "lib/libpython3.14.so.1.0"
           ]
         },
         "dynamic_stableabi": {
           "type": "string",
-          "description": "The path to the dynamic ``libpython`` library for the stable ABI.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.\n\nThis field **MUST** be present if the Python installation provides a dynamic ``libpython`` library targetting the Stable ABI, otherwise this entry will be missing.\n\nIf this key is present ``dynamic`` **MUST** also be set.",
+          "description": "The path to the dynamic ``libpython`` library for the stable ABI.\n\nEither an absolute path, or a path relative to ``base_prefix``.\n\nThis field **MUST** be present if the Python installation provides a dynamic ``libpython`` library targetting the Stable ABI, otherwise this entry will be missing.\n\nIf this key is present ``dynamic`` **MUST** also be set.",
           "examples": [
             "/usr/lib/libpython3.so",
             "lib/libpython3.so"
           ]
         },
         "static": {
           "type": "string",
-          "description": "The path to the static ``libpython`` library.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.\n\nThis field **MUST** be present if the Python installation provides a static ``libpython`` library, otherwise this entry will be missing.",
+          "description": "The path to the static ``libpython`` library.\n\nEither an absolute path, or a path relative to ``base_prefix``.\n\nThis field **MUST** be present if the Python installation provides a static ``libpython`` library, otherwise this entry will be missing.",
           "examples": [
             "/usr/lib/python3.14/config-3.14-x86_64-linux-gnu/libpython3.14.a",
             "lib/python3.14/config-3.14-x86_64-linux-gnu/libpython3.14.a"
@@ -237,15 +237,15 @@
       "properties": {
         "headers": {
           "type": "string",
-          "description": "The path to the C API headers.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.",
+          "description": "The path to the C API headers.\n\nEither an absolute path, or a path relative to ``base_prefix``.",
           "examples": [
             "/usr/include/python3.14",
             "include/python3.14"
           ]
         },
         "pkgconfig_path": {
           "type": "string",
-          "description": "The path to the pkg-config definition files.\n\nEither an absolute path, or a relative path to the path defined in the ``base_prefix`` key.\n\nThis field **MUST** be present if the Python implementation provides pkg-config definition files, otherwise this section will be missing.",
+          "description": "The path to the pkg-config definition files.\n\nEither an absolute path, or a path relative to ``base_prefix``.\n\nThis field **MUST** be present if the Python implementation provides pkg-config definition files, otherwise this section will be missing.",
           "examples": [
             "/usr/lib/pkgconfig",
             "lib/pkgconfig"