From 656c3f65ad5dc9c0470b2829e5dbca6a40763577 Mon Sep 17 00:00:00 2001 From: luz paz Date: Sat, 6 Sep 2025 08:03:16 +0200 Subject: [PATCH] Cleanup: fix typos in doc subdirectory Fix several documentation related typos. Found via `codespell -S "*.desktop,*.diff,./intern,./extern,./locale,./AUTHORS,./source/blender/blenlib/tests/BLI_string_utf8_test.cc,./doc/license/bf-members.txt" -L accessort,abd,aci,alo,ans,ba,bording,childrens,clen,constructin,datas,dependees,domin,eary,ege,eiter,elemt,eles,endianess,enew,espace,finded,fiter,fpt,groupd,hist,implementating,indext,ine,infront,inout,inouts,inpt,ist,lene,listenter,lod,maks,masia,mata,mis,mke,nam,nd,ned,opose,ot,outlow,parm,parms,passt,pinter,pixelx,poin,pres,ptd,re-usable,re-use,re-used,re-uses,re-using,ridiculus,schem,soler,strack,suh,te,tesselate,tham,ue,vai,varius,wew` Pull Request: https://projects.blender.org/blender/blender/pulls/145824 --- doc/guides/interface_API.txt | 10 +++++----- doc/python_api/examples/bpy.props.5.py | 2 +- .../info_gotchas_internal_data_and_python_objects.rst | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/doc/guides/interface_API.txt b/doc/guides/interface_API.txt index bd079ee6383..3540e73c536 100644 --- a/doc/guides/interface_API.txt +++ b/doc/guides/interface_API.txt @@ -67,7 +67,7 @@ Contents serve as permanent little button-fields in Blender windows. Think for example of having an (optional) extra field in the 3d window displaying object loc/rot/size. After that, the existing button windows can be reorganized in such blocks as well, allowing - a user to configure the genereal buttons layout (make vertical for example). + a user to configure the general buttons layout (make vertical for example). --------------1.1 C and H files @@ -263,10 +263,10 @@ uiBut *UiDefBut[CSIF]( uiBlock *block, int type, int retval, char *str, short x1, short y1, short x2, short y2, xxxx *poin, float min, float max, float a1, float a2, char *tip) -UiDefButC operatates on char -UiDefButS operatates on short -UiDefButI operatates on int -UiDefButF operatates on float +UiDefButC operates on char +UiDefButS operates on short +UiDefButI operates on int +UiDefButF operates on float *block: current uiBlock pointer type: see below diff --git a/doc/python_api/examples/bpy.props.5.py b/doc/python_api/examples/bpy.props.5.py index 87b407bee01..4d15bf180a0 100644 --- a/doc/python_api/examples/bpy.props.5.py +++ b/doc/python_api/examples/bpy.props.5.py @@ -106,7 +106,7 @@ print("test_array:", tuple(scene.test_array)) # Boolean array, using 'transform' accessors. # Note how the same result is achieved as with previous get/set example, but using default RNA storage. -# Transform accessors also have access to more informations. +# Transform accessors also have access to more information. # Also note how the stored data _is_ a two-items array. # - Set function stores a single boolean value, returned as the second component. # - Array getters must return a list or tuple. diff --git a/doc/python_api/rst/info_gotchas_internal_data_and_python_objects.rst b/doc/python_api/rst/info_gotchas_internal_data_and_python_objects.rst index 5c5d24f1424..3c6cad5e332 100644 --- a/doc/python_api/rst/info_gotchas_internal_data_and_python_objects.rst +++ b/doc/python_api/rst/info_gotchas_internal_data_and_python_objects.rst @@ -15,7 +15,7 @@ Typically, Python objects representing (wrapping) Blender data have a limited li They are created on-demand, and deleted as soon as they are not used in Python anymore. This means that storing python-only data in these objects should not be done for anything that -requires some form of persistance. +requires some form of persistence. There are some exceptions to this rule. For example, IDs do store their Python instance, once created, and re-use it instead of re-creating a new Python object every time they are accessed from Python.