summaryrefslogtreecommitdiffstatshomepage
path: root/docs/source/initialsetup
diff options
context:
space:
mode:
author Roman Donchenko <rdonchen@outlook.com>2025-09-10 03:45:36 +0300
committer GitHub <noreply@github.com>2025-09-09 20:45:36 -0400
commit109c3705ffe306f99a070b4bb65bf86c2124eed5 (patch)
tree1e3ddcb51727c33b8245384fd261f3078963111a /docs/source/initialsetup
parent94205daf2190b07f25f5890113f41e176286d1b6 (diff)
docs: fix assorted typos (#14152)
Diffstat (limited to 'docs/source/initialsetup')
-rw-r--r--docs/source/initialsetup/compilingmame.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/source/initialsetup/compilingmame.rst b/docs/source/initialsetup/compilingmame.rst
index a4559842b39..1e467fff552 100644
--- a/docs/source/initialsetup/compilingmame.rst
+++ b/docs/source/initialsetup/compilingmame.rst
@@ -577,7 +577,7 @@ Including subsets of supported systems
SUBTARGET
Set emulator subtarget to build. Some pre-defined subtargets are provided,
using Lua scripts in *scripts/target/mame* and system driver filter files in
- *src/mame*. User-defined substargets can be created using the **SOURCES**
+ *src/mame*. User-defined subtargets can be created using the **SOURCES**
or **SOURCEFILTER** option.
SOURCES
Specify system driver source files and/or folders to include. Usually used
@@ -762,7 +762,7 @@ the ``_FORTIFY_SOURCE`` macro is set in the RPM build environment, and not by
distributing a modified version of GCC.)
If you get compilation errors in ``bits/string_fortified.h`` you should first
-ensure that the ``_FORTIY_SOURCE`` macro is defined via the environment (e.g.
+ensure that the ``_FORTIFY_SOURCE`` macro is defined via the environment (e.g.
a **CFLAGS** or **CXXFLAGS** environment variable). You can check to see
whether the ``_FORTIFY_SOURCE`` macro is a built-in macro with your version of
GCC with a command like this: