From abfff1bffd85fca0ae9e1e24165b511266bedcd3 Mon Sep 17 00:00:00 2001
From: j-t-1 <120829237+j-t-1@users.noreply.github.com>
Date: Tue, 27 Feb 2024 16:19:57 +0000
Subject: [PATCH] DOC: Amend robustness documentation (#2479)

1. Remove mention of the deprecated PdfMerger.
2. Remove reference to the non-existent PdfWriter strict parameter.
---
 docs/user/robustness.md | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/docs/user/robustness.md b/docs/user/robustness.md
index 7c9b508d1..641877137 100644
--- a/docs/user/robustness.md
+++ b/docs/user/robustness.md
@@ -27,15 +27,17 @@ that they should fix their stuff.
 
 pypdf gives you the option to be strict or not.
 
-pypdf has three core objects and all of them have a `strict` parameter:
+pypdf has two core objects:
 
 * [`PdfReader`](../modules/PdfReader.md)
 * [`PdfWriter`](../modules/PdfWriter.md)
-* [`PdfMerger`](../modules/PdfMerger.md)
+
+Only the PdfReader has a `strict` parameter, since presumably you do not want
+to write a non-conforming PDF.
 
 Choosing `strict=True` means that pypdf will raise an exception if a PDF does
 not follow the specification.
 
 Choosing `strict=False` means that pypdf will try to be forgiving and do
 something reasonable, but it will log a warning message. It is a best-effort
-approach.
+approach.
\ No newline at end of file