Notes and updates based on riba's most recent comments

[dbsrgits/DBIx-Class-Manual-SQLHackers.git] / lib / DBIx / Class / Manual / SQLHackers / DELETE.pod

diff --git a/lib/DBIx/Class/Manual/SQLHackers/DELETE.pod b/lib/DBIx/Class/Manual/SQLHackers/DELETE.pod
index 09f5463..151b5fa 100644 (file)
--- a/lib/DBIx/Class/Manual/SQLHackers/DELETE.pod
+++ b/lib/DBIx/Class/Manual/SQLHackers/DELETE.pod
@@ -111,12 +111,14 @@ created by the user), should also be removed.
 NOTE: This is a rather drastic action, to prevent problems in your
 application, consider de-activating accounts instead of removing them!
 
-For the time being DBIx::Class defaults to cascade deletion for the following types
-of relationships: B<has_many>, B<has_one>, B<might_have>. That is, it
-will automatically issue the above statements. It is recommended not to rely
-on this implicit behavior, as it will be deprecated in a later version of DBIC.
-Instead declare proper cascading constraints in your RDBMS as described in
-L<DBIx::Class::Manual::SQLHackers::CREATE/Table creation with references>.
+For the time being DBIx::Class defaults to cascade deletion for the
+following types of relationships: B<has_many>, B<has_one>,
+B<might_have>. That is, it will automatically issue the above
+statements. It is recommended not to rely on this implicit behavior,
+as it will be deprecated in a later version of DBIC.  Instead declare
+proper cascading constraints in your RDBMS as described in
+L<DBIx::Class::Manual::SQLHackers::CREATE/Table creation with
+references>.
 
 If your database is already properly set up to cascade deletes for you,
 you can noop  DBIx::Class' extra cascading statements: