@@ -134,7 +134,7 @@ constraint, you'd use the code:
134134
135135 SCIP also allows the creation of custom constraint handlers. These could be empty and just
136136there to record data, there to provide custom handling of some user defined function, or they could be there to
137- enforce a constraint that is incredibly inefficient to enforce via linear constraints.
137+ enforce a constraint that is incredibly inefficient to enforce via linear constraints.
138138An example of such a constraint handler
139139is presented in the lazy constraint tutorial for modelling the subtour elimination
140140constraints :doc: `here </tutorials/lazycons >`
@@ -146,8 +146,8 @@ In a similar fashion to Variables with columns, see :doc:`this page </tutorials/
146146constraints bring up an interesting feature of SCIP when used in the context of an LP.
147147The context of an LP here means that we are after the LP relaxation of the optimization problem
148148at some node. Is the constraint even in the LP?
149- When you solve an optimization problm with SCIP, the problem is first transformed. This process is
150- called presolve, and is done to accelerate the subsequent solving process. Therefore a constraint
149+ When you solve an optimization problem with SCIP, the problem is first transformed. This process is
150+ called presolve, and is done to accelerate the subsequent solving process. Therefore, a constraint
151151that was originally created may have been transformed entirely, as the original variables that
152152featured in the constraint have also been changed. Additionally, maybe the constraint was found to be redundant,
153153i.e., trivially true, and was removed. The constraint is also much more general
0 commit comments