summaryrefslogtreecommitdiff
path: root/docs/dev/typelibraries.md
diff options
context:
space:
mode:
authorJosh Ferrell <josh@vector35.com>2025-09-11 18:29:59 -0400
committerJosh Ferrell <josh@vector35.com>2025-09-11 19:09:28 -0400
commit5f21429815bfa13bc167aff4a9785424675b82b6 (patch)
treed13caac55b8ad269062929413e286bab44ad8429 /docs/dev/typelibraries.md
parent2d20ed145b9135a7d3390acb3ac10a900d947f91 (diff)
Docs grammar and spelling fixes
Diffstat (limited to 'docs/dev/typelibraries.md')
-rw-r--r--docs/dev/typelibraries.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/dev/typelibraries.md b/docs/dev/typelibraries.md
index 7302d967..5623e087 100644
--- a/docs/dev/typelibraries.md
+++ b/docs/dev/typelibraries.md
@@ -38,7 +38,7 @@ Therefore, without any alternative names, `libc.so.bntl` will not be loaded by B
We recommend and use the following convention:
-Type libraries should be named for the filename from which they were generated with the phrase ".bntl" added. When the source library contains additional minor and release number, like `libfoo.so.1.2.3` Binary Ninja would not load the resulting type library `libfoo.so.1.2.3.bntl` for an ELF requesting soname `libfoo.so.1`. Therefore the alternative names list should include the most specific version numbers, incrementally stripped down to the soname, and finally a linkname for good measure.
+Type libraries should be named for the filename from which they were generated with the phrase ".bntl" added. When the source library contains additional minor and release number, like `libfoo.so.1.2.3` Binary Ninja would not load the resulting type library `libfoo.so.1.2.3.bntl` for an ELF requesting soname `libfoo.so.1`. Therefore, the alternative names list should include the most specific version numbers, incrementally stripped down to the soname, and finally a linkname for good measure.
Example:
@@ -285,4 +285,4 @@ When a binary is loaded and its external symbols is processed, the symbol names
type library test.bntl found hit for _DoSuperComputation
```
-At this moment, there is no built in functionality to apply named objects to an existing Binary Ninja database.
+At this moment, there is no built-in functionality to apply named objects to an existing Binary Ninja database.