mirror of
https://github.com/volatilityfoundation/volatility3.git
synced 2026-09-30 05:24:52 +02:00
fix some typo
This commit is contained in:
@@ -147,7 +147,7 @@ it does not. The :py:func:`~volatility3.plugins.windows.pslist.PsList.create_pi
|
||||
identifiers that are included in the list. If the list is empty, all processes are returned.
|
||||
|
||||
The next line specifies the columns by their name and type. The types are simple types (int, str, bytes, float, and bool)
|
||||
but can also provide hints as to how the output should be displayed (such as a hexidecimal number, using
|
||||
but can also provide hints as to how the output should be displayed (such as a hexadecimal number, using
|
||||
:py:class:`volatility3.framework.renderers.format_hints.Hex`).
|
||||
This indicates to user interfaces that the value should be displayed in a particular way, but does not guarantee that the value
|
||||
will be displayed that way (for example, if it doesn't make sense to do so in a particular interface).
|
||||
|
||||
@@ -116,7 +116,7 @@ Options
|
||||
|
||||
**<plugin>**
|
||||
The name of the plugin to execute (these are usually categorized by
|
||||
the operating system, such as `windows.pslist.PsList`). Any subtring
|
||||
the operating system, such as `windows.pslist.PsList`). Any substring
|
||||
that uniquely matches the desired plugin name can be used. As such
|
||||
`hivescan` would match `windows.registry.hivescan.HiveScan`, but
|
||||
`pslist` is ambiguous because it could match `windows.pslist` or
|
||||
|
||||
@@ -24,7 +24,7 @@ Object Model changes
|
||||
--------------------
|
||||
|
||||
The object model has changed as well, objects now inherit directly from their Python counterparts, meaning an integer
|
||||
object is actually a Python integer (and has all the associated methods, and can be used whereever a normal int could).
|
||||
object is actually a Python integer (and has all the associated methods, and can be used wherever a normal int could).
|
||||
In Volatility 2, a complex proxy object was constructed which tried to emulate all the methods of the host object, but
|
||||
ultimately it was a different type and could not be used in the same places (critically, it could make the ordering of
|
||||
operations important, since a + b might not work, but b + a might work fine).
|
||||
|
||||
Reference in New Issue
Block a user