Update ingestion filtering page to document new logic (#571)

* Update ingestion filtering doc

* Update network/horizon/admin-guide/ingestion-filtering.mdx

Co-authored-by: shawn <[email protected]>

* Small change

* Refactor error-handling move

* Refactor error-handling move - 2

* Update network/horizon/admin-guide/ingestion-filtering.mdx

Co-authored-by: Jake Urban <[email protected]>

---------

Co-authored-by: shawn <[email protected]>
Co-authored-by: Jake Urban <[email protected]>

network/horizon/admin-guide/ingestion-filtering.mdx

@@ -19,6 +19,7 @@ Filtering feature operates during ingestion in **live** and **historical range**
 
 Some key aspects to note about filtering behavior:
 
+- If both asset and account filters are enabled and each filter is provisioned with at least one rule, then transactions are stored in the database when any rule from either filter matches for the given transaction.
 - Filtering applies only to ingestion of historical data in the database, it does not affect how ingestion process maintains current state data stored in database, which is the last known ledger entry for each unique entity within accounts, trustlines, liquidity pools, offers. However, current state data consumes a relatively small amount of the overall storage capacity.
 - When filter rules are changed, they only apply to existing, running ingestion processes(**live** and **historical range**). They don't trigger any retro-active filtering or back-filling of existing historical data on the database.
   - When the filter rules are updated to include additional accounts or assets in the white-list, the related transactions from **live** ingestion will only appear in the historical database data once the filter rules have been updated using the Admin API. The same applies to **historical range** ingestion, where the new filter rules will only affect the data from the current ledger within its configured range at the time of the update.