From 2c9cf892013d8c2b7a5d499de58946fa7d438b47 Mon Sep 17 00:00:00 2001
From: DenTechs <48604154+DenTechs@users.noreply.github.com>
Date: Mon, 20 Nov 2023 21:48:52 -0500
Subject: [PATCH] Implemented Safari Monkey's suggestions
---
vitepress/docs/src/pages/getting_started/led_safety.md | 2 +-
.../docs/src/pages/how_to_build/creating_your_own_mount.md | 2 +-
vitepress/docs/src/pages/how_to_build/parts_list.md | 2 +-
.../docs/src/pages/software_guide/eyetrackvr_app_guide.md | 2 +-
vitepress/docs/src/pages/software_guide/osc_setup.md | 4 ++--
5 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/vitepress/docs/src/pages/getting_started/led_safety.md b/vitepress/docs/src/pages/getting_started/led_safety.md
index 2e72edb..89314c1 100644
--- a/vitepress/docs/src/pages/getting_started/led_safety.md
+++ b/vitepress/docs/src/pages/getting_started/led_safety.md
@@ -27,7 +27,7 @@ The safety measures were put in place to REDUCE the potential failure risk. All
We care about power exposure "W" to the cornea, which we can normalize over the exposed area to Irradiance "mW/cm^2"
This number gives us the amount of IR radiation being released into the normalized area. We don't really care about "mA", or "V" alone, as by themselves these do not give us the exposure levels which we need to ensure safety.
-Irradiance also needs to take into account distance of the light source (LED) as the further away you get from a source the weaker the intensity gets. (You can test this by looking at a light source from far away, and as you move closer, the brighter and more painful it is to look at) We do this by using Radiance "mW/cm2/sr" to normalize for the distance. The 'sr' stands for steradian, which can be thought of as a cone shape expanding as it moves away from the source
+Irradiance also needs to take into account distance of the light source (LED) as the further away you get from a source the weaker the intensity gets. (You can test this by looking at a light source from far away, and as you move closer, the brighter and more painful it is to look at) We do this by using Radiance "mW/cm2/sr" to normalize for the distance. The 'sr' stands for steradian, which can be thought of as a cone shape expanding as it moves away from the source.
The International Commission on Non-Ionizing Radiation Protection's [Guidelines of limits of exposure to broad-band incoherent optical radiation (0.38 to 3 µm)](../safety/ICNIRP_optical_radiation.pdf) states:
diff --git a/vitepress/docs/src/pages/how_to_build/creating_your_own_mount.md b/vitepress/docs/src/pages/how_to_build/creating_your_own_mount.md
index 1677494..79dcaef 100644
--- a/vitepress/docs/src/pages/how_to_build/creating_your_own_mount.md
+++ b/vitepress/docs/src/pages/how_to_build/creating_your_own_mount.md
@@ -7,7 +7,7 @@ So, you have a headset that does not have any mounts or none that work well for
## Step 1: Find a way to mount to your headset's lens
The easiest way to get started is to find a lens protector for your headset.
-You can visit a website like [Thingiverse](https://www.thingiverse.com/) or do a search for "3d printed lens protector for {your headset here}"
+You can visit a website like [Thingiverse](https://www.thingiverse.com/) or do a search for "3d printed lens protector for {your headset here}"
Example: Here is a lens protector for the Quest 1/2 and Rift S [https://www.thingiverse.com/thing:3653631](https://www.thingiverse.com/thing:3653631)
diff --git a/vitepress/docs/src/pages/how_to_build/parts_list.md b/vitepress/docs/src/pages/how_to_build/parts_list.md
index 155b0bf..b521372 100644
--- a/vitepress/docs/src/pages/how_to_build/parts_list.md
+++ b/vitepress/docs/src/pages/how_to_build/parts_list.md
@@ -112,7 +112,7 @@ Things worth noting:
- There is an experimental option to purchase OV2640 130° FOV cameras and manually remove the IR filters. This can result in a clearer view of the eye and is smaller so it allows for HMDs like the Bigscreen Beyond, but it's not a default recommendation just yet. Checkout the listing "75MM-130 Degree" [AliEXpress](https://www.aliexpress.us/item/3256804332354572.html)
-- If the cameras are Dead on Arrival (DOA), keep in mind that you can swap the lenses with the ones that come with the stock cameras that were included with the ESP32 boards though, they do require extension cables. I recommend just buying more (3-4 instead of just 2).
+- If the cameras are Dead on Arrival (DOA), keep in mind that you can swap the lenses with the ones that come with the stock cameras that were included with the ESP32 boards, though they do require extension cables. I recommend just buying more (3-4 instead of just 2).
- #### Optional Ribbon extensions:
diff --git a/vitepress/docs/src/pages/software_guide/eyetrackvr_app_guide.md b/vitepress/docs/src/pages/software_guide/eyetrackvr_app_guide.md
index 17384a1..5833a2a 100644
--- a/vitepress/docs/src/pages/software_guide/eyetrackvr_app_guide.md
+++ b/vitepress/docs/src/pages/software_guide/eyetrackvr_app_guide.md
@@ -85,7 +85,7 @@ Press the `Save and Restart Tracking` button.
### Wired configuration (experimental)
#### Note this is a Beta app feature only. Please use the latest Open Beta in the Discord.
-Find your ESPs in Device Manager and figure out their COM port numbers i.e., ``COM4``.
+Find your ESPs in Device Manager and figure out their COM port numbers, e.g. ``COM4``.
Enter that COM port number into the app's `Camera Address` field.
diff --git a/vitepress/docs/src/pages/software_guide/osc_setup.md b/vitepress/docs/src/pages/software_guide/osc_setup.md
index 5eed531..1cc7d47 100644
--- a/vitepress/docs/src/pages/software_guide/osc_setup.md
+++ b/vitepress/docs/src/pages/software_guide/osc_setup.md
@@ -30,7 +30,7 @@ To do this, in Unity, select your avatar on the scene and find Avatar Descriptor
-Clicking on it will highlight the associated asset in the asset browser, click on the highlighted file to get its content to show in the inspector panel. Now, in the inspector, click on the `Add` button to add the parameters mentioned above, both of them need to be of type Bool, they don't need to be synced nor saved.
+Clicking on it will highlight the associated asset in the asset browser. Click on the highlighted file to get its content to show in the inspector panel. Now, in the inspector, click on the `Add` button to add the parameters mentioned above. Both of them need to be of type Bool, but they don't need to be synced nor saved.
@@ -66,7 +66,7 @@ And that's it, you now should be able to recenter and recalibrate your tracking
## Resetting the OSC config in case the parameters don't work
-Sometimes VRChat won't regenerate the config files that it to communicate the changes to anyone that's listening, to fix this it's enough to simply delete the auto generated configuration files and let VRC remake them.
+Sometimes VRChat won't regenerate the config files that it uses to communicate the changes to anyone that's listening. To fix this, it's enough to simply delete the auto generated configuration files and let VRC remake them.
They are stored under