summaryrefslogtreecommitdiff
path: root/docs/guide
diff options
context:
space:
mode:
authorJordan Wiens <jordan@psifertex.com>2025-03-31 11:17:10 -0400
committerJordan Wiens <jordan@psifertex.com>2025-03-31 11:17:10 -0400
commita96818fc7a696f6f925c024767145c82fe39b523 (patch)
tree6c1d6d9f0e9eb2721192848bca1fe810249ef71a /docs/guide
parentaa58173a9eebac49b367671ae2b894abffd1d6e9 (diff)
small phrasing update
Diffstat (limited to 'docs/guide')
-rw-r--r--docs/guide/types/type.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/guide/types/type.md b/docs/guide/types/type.md
index 4b41feb1..e89738fb 100644
--- a/docs/guide/types/type.md
+++ b/docs/guide/types/type.md
@@ -50,7 +50,7 @@ It works in the following ways:
| Linear/Graph/Types | A variable, data variable, or a type name | struct/struct\* | Create all members for structure |
| Linear/Graph/Types | A StructOffsetToken token, e.g., `__offset(0x18)` | N/A | Create current member for structure |
-Below are detailed explanation of it:
+Here's a more detailed explanation about the various workflows:
1. In linear/graph view, if the selection is a variable that is not a structure, a dialog pops up and asks you to create a structure. You can specify the structure's name and size. There is also a checkbox that asks you whether the variable's type should be the structure itself or a pointer to the structure.
2. In linear/graph view, if the selection is a variable that is not a structure, and it happens to be the result of a memory allocation routine, e.g., `malloc`, a new structure will be created and its size is automatically determined (if possible). The variable's type will be a pointer to the structure.
@@ -91,4 +91,4 @@ This also works within data variables with structure type. For example, if the s
Many characters commonly used in function naming are not valid C characters. For example, `::` in C++ types, braces or brackets. While we use clang's type-parser for such APIs as [parse_type_string](https://api.binary.ninja/binaryninja.binaryview-module.html#binaryninja.binaryview.BinaryView.parse_type_string) (note there's also [another version](https://api.binary.ninja/binaryninja.typeparser-module.html#binaryninja.typeparser.TypeParser.parse_type_string) of that API independent of the BinaryView off of the TypeParser module).
-To resolve this, we use `` ` `` (the backtick character) to enclose strings that should be treated as atomic units in the type-parser. You may notice this yourself if you by creating a struct with `:` in the name and then using `n` on the variable to see how it is escaped in the change name dialog. \ No newline at end of file
+To resolve this, we use `` ` `` (the backtick character) to enclose strings that should be treated as atomic units in the type-parser. You may notice this yourself if you by creating a struct with `:` in the name and then using `n` on the variable to see how it is escaped in the change name dialog.