godotengine/godot-docs
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs.git synced 2026-01-04 14:11:02 +03:00
Code Issues Packages Projects Releases Wiki Activity

Cleanup uses of double spaces between words or after punctuation

Browse Source
This commit is contained in:
Rémi Verschelde
2021-06-07 10:15:21 +02:00
committed by Hugo Locurcio
parent fd2981257f
commit e2b95576d8
26 changed files with 111 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
tutorials/vr/developing_for_oculus_quest.rst
View File

@@ -81,7 +81,7 @@ is the scene we run. Godot does not ask you to set this on export.
.. image:: img/quest_project_settings.png
Then go into the export menu and configure a new Android export. if
Then go into the export menu and configure a new Android export. If
you still haven't gone through the :ref:`doc_exporting_for_android`
page do it now. If you didn't you'll have some red messages on this
screen.

2
tutorials/vr/vr_starter_tutorial/vr_starter_tutorial_part_one.rst
View File

@@ -770,7 +770,7 @@ teleport, it will make the ``teleport_mesh`` visible so the user knows where the
_________________
If ``held_object`` is not equal to ``null``, then the VR controller is holding something. We then check to see if the object that is being held, ``held_object``, extends
a class called ``VR_Interactable_Rigidbody``. we have not made ``VR_Interactable_Rigidbody`` yet, but ``VR_Interactable_Rigidbody`` will be a custom class we will use
a class called ``VR_Interactable_Rigidbody``. We have not made ``VR_Interactable_Rigidbody`` yet, but ``VR_Interactable_Rigidbody`` will be a custom class we will use
on all of the special/custom :ref:`RigidBody <class_RigidBody>`-based nodes in the project.
.. tip:: Don't worry, we will cover ``VR_Interactable_Rigidbody`` after this section!

2
tutorials/vr/vr_starter_tutorial/vr_starter_tutorial_part_two.rst
View File

@@ -848,7 +848,7 @@ that the functions defined defined in ``VR_Interactable_Rigidbody`` can be calle
Next, let's look at the class variables:
* ``SWORD_DAMAGE``: A constant to define the amount of damage the sword does. This damage is applied to every object in the sword on every ``_physics_process`` call
* ``SWORD_DAMAGE``: A constant to define the amount of damage the sword does. This damage is applied to every object in the sword on every ``_physics_process`` call
* ``COLLISION_FORCE``: A constant that defines the amount of force applied to :ref:`RigidBody <class_RigidBody>` nodes when the sword collides with a :ref:`PhysicsBody <class_PhysicsBody>`.
* ``damage_body``: A variable to hold the :ref:`KinematicBody <class_KinematicBody>` node used to detect whether the sword is stabbing a :ref:`PhysicsBody <class_PhysicsBody>` node or not.
* ``sword_noise``: A variable to hold the :ref:`AudioStreamPlayer3D <class_AudioStreamPlayer3D>` node used to play a sound when the sword collides with something.