diff --git a/src/backends/plonky2/mock/mainpod.rs b/src/backends/plonky2/mock/mainpod.rs
index 2fe6807..ddd3c39 100644
--- a/src/backends/plonky2/mock/mainpod.rs
+++ b/src/backends/plonky2/mock/mainpod.rs
@@ -148,7 +148,6 @@ impl MockMainPod {
 
     pub fn new(params: &Params, inputs: MainPodInputs) -> Result<Self> {
         let (statements, public_statements) = layout_statements(params, true, &inputs)?;
-        dbg!(public_statements.len());
         let mut aux_list = vec![OperationAux::None; params.max_priv_statements()];
         // Extract Merkle proofs and pad.
         let merkle_proofs =
diff --git a/src/frontend/custom.rs b/src/frontend/custom.rs
index 8f259e1..fa75d8f 100644
--- a/src/frontend/custom.rs
+++ b/src/frontend/custom.rs
@@ -119,14 +119,10 @@ impl StatementTmplBuilder {
                 predicate: Predicate::Native(NativePredicate::ContainerDelete),
                 args: self.args,
             },
-            Predicate::Native(NativePredicate::SetDelete) => {
-                let mut new_args = self.args.clone();
-                new_args.push(self.args[2].clone());
-                StatementTmplBuilder {
-                    predicate: Predicate::Native(NativePredicate::ContainerDelete),
-                    args: new_args,
-                }
-            }
+            Predicate::Native(NativePredicate::SetDelete) => StatementTmplBuilder {
+                predicate: Predicate::Native(NativePredicate::ContainerDelete),
+                args: self.args,
+            },
             _ => self,
         }
     }
diff --git a/src/middleware/basetypes.rs b/src/middleware/basetypes.rs
index 97ed113..d2d4eed 100644
--- a/src/middleware/basetypes.rs
+++ b/src/middleware/basetypes.rs
@@ -2,7 +2,7 @@
 //! from the feature-enabled backend.
 //!
 //! This is done in order to avoid inconsistencies where a type or parameter is defined in the
-//! middleware to have certain carachteristic and later in the backend it gets used differently.
+//! middleware to have certain characteristic and later in the backend it gets used differently.
 //! The idea is that those types and parameters (eg. lengths) have a single source of truth in the
 //! code; and in the case of the "base types" this is determined by the backend being used under
 //! the hood, not by a choice of the middleware parameters.