Преглед изворни кода

Update docs/configuring-playbook-bridge-beeper-linkedin.md: follow other instances

Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
pull/3837/head
Suguru Hirahara пре 1 година
родитељ
комит
b46370005a
No known key found for this signature in database GPG Key ID: E4F9743DAB4B7B75
1 измењених фајлова са 1 додато и 1 уклоњено
  1. +1
    -1
      docs/configuring-playbook-bridge-beeper-linkedin.md

+ 1
- 1
docs/configuring-playbook-bridge-beeper-linkedin.md Прегледај датотеку

@@ -39,7 +39,7 @@ After configuring the playbook, run the [installation](installing.md) command: `


## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth ## Set up Double Puppeting by enabling Appservice Double Puppet or Shared Secret Auth


The bridge automatically performs Double Puppeting if you enable [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service for this playbook.
The bridge automatically performs Double Puppeting if [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) or [Shared Secret Auth](configuring-playbook-shared-secret-auth.md) service is configured and enabled on the server for this playbook.


Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future. Enabling [Appservice Double Puppet](configuring-playbook-appservice-double-puppet.md) is the recommended way of setting up Double Puppeting, as it's easier to accomplish, works for all your users automatically, and has less of a chance of breaking in the future.




Loading…
Откажи
Сачувај