Skip to content

Commit a789919

Browse files
author
cabailey
committed
formatting fixes
1 parent 051dbda commit a789919

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

exchange/docs-conceptual/client-advanced-settings.md

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ With this setting, the following extensions always become **P\<EXT>**: ".txt", "
8787
Set-LabelPolicy -AdvancedSettings @{ AdditionalPPrefixExtensions =""}
8888
```
8989

90-
**Example 2**: PowerShell command to change all PFile extensions from generic encryption (dwg.pfile) to native encryption (.pdwg) when the files are protected:
90+
**Example 2**: PowerShell command to change all PFile extensions from generic encryption to native encryption when the files are labeled and encrypted:
9191

9292
```PowerShell
9393
Set-LabelPolicy -AdvancedSettings @{ AdditionalPPrefixExtensions ="*"}
@@ -183,7 +183,7 @@ Set-LabelPolicy -Identity Global -AdvancedSettings @{EnableCustomPermissions="Fa
183183

184184
## EnableCustomPermissionsForCustomProtectedFiles
185185

186-
When you configure the advanced client setting to [turn off custom permissions in File Explorer](#turn-off-custom-permissions-in-file-explorer), by default, users are not able to see or change custom permissions that are already set in an encrypted document.
186+
When you configure the advanced client setting *EnableCustomPermissionsto* to turn off custom permissions in File Explorer, by default, users are not able to see or change custom permissions that are already set in an encrypted document.
187187

188188
However, there's another advanced client setting that you can specify so that in this scenario, users can see and change custom permissions for an encrypted document when they use File Explorer and right-click the file.
189189

@@ -219,18 +219,17 @@ To turn off support again and revert to the default, set the **EnableGlobalizati
219219

220220
Customize the justification prompts that are displayed when end users change sensitivity labels on files.
221221

222-
For example, as an administrator, you might want to remind your users not to add any customer identifying information into this field:
222+
For example, as an administrator, you might want to remind your users not to add any customer identifying information into this field.
223223

224-
:::image type="content" source="../media/justification-office.png" alt-text="Customized justification prompt text":::
225-
226-
To modify the default **Other** text that's displayed, use the *JustificationTextForUserText* advanced setting. Set the value to the text you want to use instead.
224+
To modify the default **Other** option that users can select in the dialog box, use the *JustificationTextForUserText* advanced setting. Set the value to the text you want to use instead.
227225

228226
Example PowerShell command, where your label policy is named "Global":
229227

230228
``` PowerShell
231229
Set-LabelPolicy -Identity Global -AdvancedSettings @{JustificationTextForUserText="Other (please explain) - Do not enter sensitive info"}
232230
```
233231

232+
234233
## PFileSupportedExtensions
235234

236235
- Key: **PFileSupportedExtensions**
@@ -289,7 +288,7 @@ Use this advanced setting in conjunction with *ScannerMinCPU* to limit CPU consu
289288

290289
- Key: **ScannerMaxCPU**
291290

292-
- Value: <number>**
291+
- Value: \<number>**
293292

294293
The value is set to **100** by default, which means there is no limit of maximum CPU consumption. In this case, the scanner process will try to use all available CPU time to maximize your scan rates.
295294

0 commit comments

Comments
 (0)