chore(docs): rename args filter to data filter

docs/docs/events/builtin/extra/symbols_collision.md

@@ -9,14 +9,14 @@ with other shared object already loaded to the process. This event can help in i
 occasion that a shared object tries to override some symbol of another library.
 
 ### Configuring the event
-The event is configured using arguments filtering.
+The event is configured using data filtering.
 #### symbols
 Configure the watched symbols that upon collision will trigger the event.
 Specify the full name of the symbol for each symbol.
 Notice that only watched symbols will be outputed by the event, and the default is watching all symbols.
 The use is only with the `=` or `!=` operators, and wildcards aren't supported.
 
-## Arguments
+## Data
 * `loaded_path`:`const char*`[K] - the path of the file loaded.
 * `collision_path`:`const char*`[K,TOCTOU] - the path of the file already loaded, which has collision with the new loaded one.
 * `symbols`:`const char*const*`[U,TOCTOU] - list of symbols collided between the files.

docs/docs/events/builtin/extra/symbols_loaded.md

@@ -10,8 +10,8 @@ usage in the system, or inform on the occasion that a shared object tries to ove
 some symbol of another library.
 
 ### Configuring the event
-The event is configured using arguments filtering.
-For each argument, a filter can be used to configure the operation:
+The event is configured using data filtering.
+For each data, a filter can be used to configure the operation:
 #### symbols
 Configure the watched symbols by the event.
 Specify the full name of the symbol for each symbol.
@@ -23,7 +23,7 @@ If only a name is given, then any shared object inside the known libraries direc
 starts with the prefix will be whitelisted.
 The use is only with the `!=` operator, and wildcards aren't supported.
 
-## Arguments
+## Data
 * `library_path`:`const char*`[K] - the path of the shared object file loaded.
 * `symbols`:`const char*const*`[U,TOCTOU] - the watched symbols exported by the shared object.
 

docs/docs/policies/rules.md

@@ -6,7 +6,7 @@ Below are several examples on configuring events in the Tracee Policy.
 
 ## Events
 
-Every event that is specified within the `rules` section supports three types of filters: `scope`, `arguments` and `return value`. 
+Every event that is specified within the `rules` section supports three types of filters: `scope`, `data` and `return value`.
 
 ### Type of Events
 
@@ -239,17 +239,17 @@ filters:
 ```
 
 
-## Argument filter
+## Data filter
 
-Events have arguments, which can be filtered. 
+Events contain data that can be filtered.
 
 ```yaml
 apiVersion: tracee.aquasec.com/v1beta1
 kind: Policy
 metadata:
-	name: sample-argument-filter
+	name: sample-data-filter
 	annotations:
-		description: sample argument filter
+		description: sample data filter
 spec:
 	scope:
 	    - global

pkg/ebpf/events_pipeline.go

@@ -341,7 +341,7 @@ func (t *Tracee) matchPolicies(event *trace.Event) uint64 {
 			continue
 		}
 
-		// 3. event arguments filters
+		// 3. event data filters
 		if !p.DataFilter.Filter(eventID, event.Args) {
 			utils.ClearBit(&bitmap, bitOffset)
 			continue