Fix typos & spelling mistakes
This commit is contained in:
parent
7fe2292604
commit
6b31c6f7f2
@ -1178,7 +1178,7 @@ bbb-conf --restart
|
||||
Start a new meeting on the server, switch to German localization in Settings, **clear the cache** if needed -- frequently locales are cached.
|
||||
|
||||
Please use caution when replacing/editing locales. If you followed the steps above you should have a backup copy of `de.json` (with ".old" appended) in `/tmp` in case you need to revert.
|
||||
Note that the json files accross BigBlueButton versions are not always interchangeable. The workflow described above is only really meant for cases like
|
||||
Note that the json files across BigBlueButton versions are not always interchangeable. The workflow described above is only really meant for cases like
|
||||
- I would like to tweak a translation for my own use
|
||||
- I would like to adopt a change from upstream without having to wait for the official release in a few days
|
||||
- This is part of my customization setup and I know what I need to test. I also know how to recover if needed
|
||||
@ -1373,7 +1373,7 @@ Useful tools for development:
|
||||
| `userdata-bbb_skip_check_audio=` | If set to `true`, the user will not see the "echo test" prompt when sharing audio | `false` |
|
||||
| `userdata-bbb_skip_check_audio_on_first_join=` | (Introduced in BigBlueButton 2.3) If set to `true`, the user will not see the "echo test" when sharing audio for the first time in the session. If the user stops sharing, next time they try to share audio the echo test window will be displayed, allowing for configuration changes to be made prior to sharing audio again | `false` |
|
||||
| `userdata-bbb_override_default_locale=` | (Introduced in BigBlueButton 2.3) If set to `de`, the user's browser preference will be ignored - the client will be shown in 'de' (i.e. German) regardless of the otherwise preferred locale 'en' (or other) | `null` |
|
||||
| `userdata-bbb_hide_presentation_on_join` | (Introduced in BigBlueButton 2.6) If set to `true` it will make the user enter the meeting with presentation minimized (Only for non-presenters), not peremanent.
|
||||
| `userdata-bbb_hide_presentation_on_join` | (Introduced in BigBlueButton 2.6) If set to `true` it will make the user enter the meeting with presentation minimized (Only for non-presenters), not permanent.
|
||||
|
||||
| `userdata-bbb_direct_leave_button` | (Introduced in BigBlueButton 2.7) If set to `true` it will make a button to leave the meeting appear to the left of the Options menu. | `false` | | `false` |
|
||||
|
||||
@ -1418,7 +1418,7 @@ Useful tools for development:
|
||||
| `userdata-bbb_presenter_tools=` | Pass in an array of permitted tools from `settings.yml` | all enabled |
|
||||
| `userdata-bbb_multi_user_tools=` | Pass in an array of permitted tools for non-presenters from `settings.yml` | all enabled |
|
||||
|
||||
#### Themeing & styling parameters
|
||||
#### Theming & styling parameters
|
||||
|
||||
| Parameter | Description | Default value |
|
||||
| -------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ------------- |
|
||||
|
@ -29,7 +29,7 @@ We have made changes so that when you set yourself as being Away, your microphon
|
||||
|
||||
![set yourself away](/img/30/30-set-away.png)
|
||||
|
||||
When you return and unmute youself this counts as disabling Away mode. The control for toggling away mode is now positioned in the Reactions bar.
|
||||
When you return and unmute yourself this counts as disabling Away mode. The control for toggling away mode is now positioned in the Reactions bar.
|
||||
|
||||
![set yourself active](/img/30/30-set-active.png)
|
||||
|
||||
|
@ -12,7 +12,7 @@ keywords:
|
||||
|
||||
Have you encountered a problem with BigBluebutton?
|
||||
|
||||
If you need the problem to be solved quickly or lack the requirded technical knowledge, we suggest you [reach out to the companies](https://bigbluebutton.org/commercial-support/) that provide commercial support. The revenue they earn helps to improve BigBlueButton for everyone.
|
||||
If you need the problem to be solved quickly or lack the required technical knowledge, we suggest you [reach out to the companies](https://bigbluebutton.org/commercial-support/) that provide commercial support. The revenue they earn helps to improve BigBlueButton for everyone.
|
||||
|
||||
If you otherwise wish to tackle the problem yourself, the BigBlueButton project provides detailed documentation (what you are reading now), tutorial videos, [issues database](https://github.com/bigbluebutton/bigbluebutton/issues), and [public mailing lists](https://bigbluebutton.org/community-support/).
|
||||
|
||||
|
@ -160,7 +160,7 @@ For example:
|
||||
|
||||
No. Scalability improves a lot with mediasoup, but there are still a couple of bottlenecks that can be hit as far **as far as the media stack is concerned**. Namely:
|
||||
- The signaling server (bbb-webrtc-sfu): it does not scale vertically indefinitely.
|
||||
- The mediasoup worker balancing algorithm implemented by bbb-webrtc-sfu is still focused on multiparty meetings with a restrained number of users. If your goal is thousand-user 1-N (streaming-like) meetings, you may max out CPU usage on certain mediasoup workers even though there are other idle oworkers free.
|
||||
- The mediasoup worker balancing algorithm implemented by bbb-webrtc-sfu is still focused on multiparty meetings with a restrained number of users. If your goal is thousand-user 1-N (streaming-like) meetings, you may max out CPU usage on certain mediasoup workers even though there are other idle workers free.
|
||||
|
||||
### bbb-webrtc-sfu fails to start with a SETSCHEDULER error
|
||||
|
||||
|
@ -228,7 +228,7 @@ You should now have presenter capabilities and presenter icon should appear over
|
||||
|
||||
5. Click the webcam's fullscreen button again.
|
||||
|
||||
6. Click the undo fulscreen button ("Undo [user name] fullscreen").
|
||||
6. Click the undo fullscreen button ("Undo [user name] fullscreen").
|
||||
|
||||
7. The webcam should exit the fullscreen and go back to normal size.
|
||||
|
||||
@ -471,7 +471,7 @@ The screen sharing stops, a sound effect of disconnection is heard and the prese
|
||||
|
||||
2. Inside the breakout rooms control panel ("Breakout Rooms" button in the left-hand panel), select the "Breakout options" dropdown and choose "Destroy breakouts".
|
||||
|
||||
3. All of the breaout rooms should end and all users should get back to the main room. If users already got the audio on, they shouldn't get prompted for the audio modal.
|
||||
3. All of the breakout rooms should end and all users should get back to the main room. If users already got the audio on, they shouldn't get prompted for the audio modal.
|
||||
|
||||
### Edit the duration of a breakout room
|
||||
|
||||
@ -519,7 +519,7 @@ The screen sharing stops, a sound effect of disconnection is heard and the prese
|
||||
|
||||
4. Change the microphone and speaker using the dropdowns (if applicable).
|
||||
|
||||
5. Press "Stop audio feedback button" and verify that you dont hear your audio anymore, while the audio stream volume bar is still functional. Clicking that button again should turn on the audio feedback again.
|
||||
5. Press "Stop audio feedback button" and verify that you don't hear your audio anymore, while the audio stream volume bar is still functional. Clicking that button again should turn on the audio feedback again.
|
||||
|
||||
6. Click "Yes".
|
||||
|
||||
@ -1116,7 +1116,7 @@ Share notes should export and download in the chosen format.
|
||||
|
||||
8. Moderator: demote another moderator (click on the user name in the user list and select "Demote to viewer").
|
||||
|
||||
9. Demoted moderator: shouldn't be able to send private chat messages to viewrs.
|
||||
9. Demoted moderator: shouldn't be able to send private chat messages to viewers.
|
||||
|
||||
10. Moderator: promote a viewer (click on the user name in the user list and select "Promote to moderator").
|
||||
|
||||
@ -1222,7 +1222,7 @@ Share notes should export and download in the chosen format.
|
||||
|
||||
4. Moderator: toggle one of the lock setting (it becomes "Locked"), click "Apply".
|
||||
|
||||
5. Moderator: click on a vewer's user name in the user list, then select "Unlock User [user name]".
|
||||
5. Moderator: click on a viewer's user name in the user list, then select "Unlock User [user name]".
|
||||
|
||||
6. Unlocked user: should be able to use the features that were previously unlocked.
|
||||
|
||||
@ -1470,7 +1470,7 @@ Note :
|
||||
|
||||
1. Join meeting.
|
||||
|
||||
2. Click on the "Options" button in the top-right corver of the client (three dots icon).
|
||||
2. Click on the "Options" button in the top-right corner of the client (three dots icon).
|
||||
|
||||
3. Dropdown list should appear with a list of available options.
|
||||
|
||||
@ -1667,7 +1667,7 @@ Note :
|
||||
|
||||
10. Moderator: type in the textbox, press Enter or click "Send" button. The message should be visible to all waiting viewers on their lobby screens (as well as in the moderator's waiting users panel).
|
||||
|
||||
11. Moderator: click "Message" for a specific viewer in the list, type in the textbox, press Enter or click "Send" button. The message should appear only for that cpecific viewer.
|
||||
11. Moderator: click "Message" for a specific viewer in the list, type in the textbox, press Enter or click "Send" button. The message should appear only for that specific viewer.
|
||||
|
||||
- Click "Deny everyone". All the waiting viewers should see the message "Guest denied of joining the meeting" and should soon be redirected to the home page. All new viewers should not be effected by this, but instead they should be placed in the waiting lobby.
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user