summaryrefslogtreecommitdiff
path: root/pyuno
diff options
context:
space:
mode:
Diffstat (limited to 'pyuno')
-rw-r--r--pyuno/GeneratedPackage_python-core.mk2
-rw-r--r--pyuno/README2
2 files changed, 2 insertions, 2 deletions
diff --git a/pyuno/GeneratedPackage_python-core.mk b/pyuno/GeneratedPackage_python-core.mk
index 88cd9b9898d2..ec6123ed3921 100644
--- a/pyuno/GeneratedPackage_python-core.mk
+++ b/pyuno/GeneratedPackage_python-core.mk
@@ -12,7 +12,7 @@ $(eval $(call gb_GeneratedPackage_GeneratedPackage,python-core,$(MINGW_SYSROOT)/
# NOTE: The original code excluded *.pyc, *.py~, *.orig and *_failed . I
# assume it was just a size optimization. If their presence actually
# causes a problem, an extension of GeneratedPackage is is left as an
-# excercise for the poor misguided person who wants to cross-compile
+# exercise for the poor misguided person who wants to cross-compile
# with mingw and system python and actually use the results for
# something.
$(eval $(call gb_GeneratedPackage_add_dir,python-core,$(INSTDIR)/program/python-core-$(PYTHON_VERSION)/lib,python$(PYTHON_VERSION_MAJOR).$(PYTHON_VERSION_MINOR)))
diff --git a/pyuno/README b/pyuno/README
index 26f929a28fd8..4d88391229f1 100644
--- a/pyuno/README
+++ b/pyuno/README
@@ -13,7 +13,7 @@ that is copied to instdir and will be auto-loaded by gdb;
it provides commands like "py-bt" to get a python-level backtrace,
and "py-print" to print python variables.
-Another way to debug python code is to use pdb: edit some initalization
+Another way to debug Python code is to use pdb: edit some initialization
function to insert "import pdb; pdb.set_trace()" (somewhere so that it is
executed early), then run soffice from a terminal and a command-line python
debugger will appear where you can set python-level breakpoints.