docs(suffix-subjects): document expected behavior about Finnish compatibility

See #109

Author: JasonWeinzierl

docs/rules/finnish.md

@@ -68,19 +68,6 @@ The default (Angular-friendly) configuration looks like this:
 
 The properties in the options object are themselves optional; they do not all have to be specified.
 
-Note the default options of this rule will conflict with [`suffix-subjects`](./suffix-subjects.md).
-If you want to handle subjects separately with `suffix-subjects` (or another rule),
-then add the following to your `finnish` options:
-
-```js
-    "types": {
-        // The default allowed types.
-        "^EventEmitter$": false,
-        // The subject types to be compatible with suffix-subjects.
-        "^(BehaviorSubject|ReplaySubject|AsyncSubject|Subject)$": false,
-    }
-```
-
 ## When Not To Use It
 
 If you don't use Finnish notation in your project or don't care about enforcing Finnish notation in your project, you don't need this rule.

docs/rules/suffix-subjects.md

@@ -6,6 +6,10 @@
 
 This rule effects failures if subject variables, properties and parameters don't conform to a naming scheme that identifies them as subjects.
 
+> [!NOTE]
+> This rule is designed to be optionally compatible with [`finnish`](./finnish.md).
+> Using Finnish notation (adding a `$` suffix) your subject names will _not_ cause a failure of this rule.
+
 ## Rule details
 
 Examples of **incorrect** code for this rule:
@@ -18,6 +22,7 @@ Examples of **correct** code for this rule:
 
 ```ts
 const answersSubject = new Subject<number>();
+const answersSubject$ = new Subject<number>();
 ```
 
 ## Options
@@ -57,9 +62,6 @@ The default (Angular-friendly) configuration looks like this:
 
 The properties in the options object are themselves optional; they do not all have to be specified.
 
-Note this rule will conflict with [`finnish`](./finnish.md) with default options.
-See that rule for notes on how to configure both rules.
-
 ## When Not To Use It
 
 If you don't use suffixes on your project's subjects, then you don't need this rule.