diff mbox series

Documentation: Remove repeated word in docs

Message ID 20250206091530.4826-1-hanchunchao@inspur.com (mailing list archive)
State Not Applicable, archived
Headers show
Series Documentation: Remove repeated word in docs | expand

Commit Message

Charles Han Feb. 6, 2025, 9:15 a.m. UTC
Remove the repeated word "to" docs.

Signed-off-by: Charles Han <hanchunchao@inspur.com>
---
 .../devicetree/bindings/net/can/microchip,mcp251xfd.yaml        | 2 +-
 Documentation/filesystems/xfs/xfs-online-fsck-design.rst        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Comments

Marc Kleine-Budde Feb. 6, 2025, 9:30 a.m. UTC | #1
On 06.02.2025 17:15:29, Charles Han wrote:
> Remove the repeated word "to" docs.
> 
> Signed-off-by: Charles Han <hanchunchao@inspur.com>

Feel free to take the patch.

Acked-by: Marc Kleine-Budde <mkl@pengutronix.de>

regards,
Marc
Vincent Mailhol Feb. 6, 2025, 10:56 a.m. UTC | #2
On 06/02/2025 at 18:15, Charles Han wrote:
> Remove the repeated word "to" docs.
> 
> Signed-off-by: Charles Han <hanchunchao@inspur.com>
> ---
>  .../devicetree/bindings/net/can/microchip,mcp251xfd.yaml        | 2 +-
>  Documentation/filesystems/xfs/xfs-online-fsck-design.rst        | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
> index 2a98b26630cb..c155c9c6db39 100644
> --- a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
> +++ b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
> @@ -40,7 +40,7 @@ properties:
>  
>    microchip,rx-int-gpios:
>      description:
> -      GPIO phandle of GPIO connected to to INT1 pin of the MCP251XFD, which
> +      GPIO phandle of GPIO connected to INT1 pin of the MCP251XFD, which
>        signals a pending RX interrupt.
>      maxItems: 1
>  
> diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> index 12aa63840830..994f9e5638ee 100644
> --- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> +++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> @@ -4521,7 +4521,7 @@ Both online and offline repair can use this strategy.
>  | For this second effort, the ondisk parent pointer format as originally   |
>  | proposed was ``(parent_inum, parent_gen, dirent_pos) → (dirent_name)``.  |
>  | The format was changed during development to eliminate the requirement   |
> -| of repair tools needing to to ensure that the ``dirent_pos`` field       |
> +| of repair tools needing to ensure that the ``dirent_pos`` field       |

This breaks the indentation of the pipe on the right.

>  | always matched when reconstructing a directory.                          |
>  |                                                                          |
>  | There were a few other ways to have solved that problem:                 |


Yours sincerely,
Vincent Mailhol
Bagas Sanjaya Feb. 7, 2025, 1:25 a.m. UTC | #3
On Thu, Feb 06, 2025 at 07:56:36PM +0900, Vincent Mailhol wrote:
> On 06/02/2025 at 18:15, Charles Han wrote:
> > diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> > index 12aa63840830..994f9e5638ee 100644
> > --- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> > +++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
> > @@ -4521,7 +4521,7 @@ Both online and offline repair can use this strategy.
> >  | For this second effort, the ondisk parent pointer format as originally   |
> >  | proposed was ``(parent_inum, parent_gen, dirent_pos) → (dirent_name)``.  |
> >  | The format was changed during development to eliminate the requirement   |
> > -| of repair tools needing to to ensure that the ``dirent_pos`` field       |
> > +| of repair tools needing to ensure that the ``dirent_pos`` field       |
> 
> This breaks the indentation of the pipe on the right.

Indeed because Sphinx spills out malformed table error:

Documentation/filesystems/xfs/xfs-online-fsck-design.rst:4479: ERROR: Malformed table.
> <snipped>...
| For this second effort, the ondisk parent pointer format as originally   |
| proposed was ``(parent_inum, parent_gen, dirent_pos) → (dirent_name)``.  |
| The format was changed during development to eliminate the requirement   |
| of repair tools needing to ensure that the ``dirent_pos`` field       |
| always matched when reconstructing a directory.                          |
|                                                                          |
| There were a few other ways to have solved that problem:                 |
> <snipped>... 

Hence I didn't see that historical sidebar in htmldocs output.

Thanks.
diff mbox series

Patch

diff --git a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
index 2a98b26630cb..c155c9c6db39 100644
--- a/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
+++ b/Documentation/devicetree/bindings/net/can/microchip,mcp251xfd.yaml
@@ -40,7 +40,7 @@  properties:
 
   microchip,rx-int-gpios:
     description:
-      GPIO phandle of GPIO connected to to INT1 pin of the MCP251XFD, which
+      GPIO phandle of GPIO connected to INT1 pin of the MCP251XFD, which
       signals a pending RX interrupt.
     maxItems: 1
 
diff --git a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
index 12aa63840830..994f9e5638ee 100644
--- a/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
+++ b/Documentation/filesystems/xfs/xfs-online-fsck-design.rst
@@ -4521,7 +4521,7 @@  Both online and offline repair can use this strategy.
 | For this second effort, the ondisk parent pointer format as originally   |
 | proposed was ``(parent_inum, parent_gen, dirent_pos) → (dirent_name)``.  |
 | The format was changed during development to eliminate the requirement   |
-| of repair tools needing to to ensure that the ``dirent_pos`` field       |
+| of repair tools needing to ensure that the ``dirent_pos`` field       |
 | always matched when reconstructing a directory.                          |
 |                                                                          |
 | There were a few other ways to have solved that problem:                 |