github/concrete
1
1
Fork 0
mirror of https://github.com/zama-ai/concrete.git synced 2026-01-08 20:38:06 -05:00
Code Issues Packages Projects Releases Wiki Activity

docs(frontend): fix spelling issues

Browse Source
This commit is contained in:
Elias Rad
2024-10-03 00:20:05 +03:00
committed by Alex Quint
parent 925a37d232
commit 65a5d5514d
4 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/core-features/bitwise.md
View File

@@ -443,7 +443,7 @@ Different strategies are good for different circuits. If you want the best runti
## Shifts
The same configuration option is used to modify the behavior of encrypted shift operations, and shifts are much more complex to implement, so we'll not go over the details. What is important is, the end the result is computed using additions or subtractions on the original shifted operand. Since additions and subtractions require the same bit-width across operands, input and output bit-widths need to be synchronized at some point. There are two ways to do this:
The same configuration option is used to modify the behavior of encrypted shift operations, and shifts are much more complex to implement, so we'll not go over the details. What is important is, that the end result is computed using additions or subtractions on the original shifted operand. Since additions and subtractions require the same bit-width across operands, input and output bit-widths need to be synchronized at some point. There are two ways to do this:
### With promotion

2
docs/core-features/extensions.md
View File

@@ -567,7 +567,7 @@ Identity extension only works in `Native` encoding, which is usually selected wh
It is similar to `fhe.identity` but with the extra guarantee that encryption noise is refreshed.
{% hint style="info" %}
Refresh is useful when you want to control precisely where encryption noise is refreshed in your circuit. For instance if your are using modules, sometimes compilation rejects the module because it's *not composable*. This happens because a function of the module never refresh the encryption noise. Adding a `return fhe.refresh(result)` on the function result solves the issue.
Refresh is useful when you want to control precisely where encryption noise is refreshed in your circuit. For instance if you are using modules, sometimes compilation rejects the module because it's *not composable*. This happens because a function of the module never refresh the encryption noise. Adding a `return fhe.refresh(result)` on the function result solves the issue.
{% endhint %}
{% hint style="warning" %}

2
docs/core-features/rounding.md
View File

@@ -341,7 +341,7 @@ The off-centering is:
## Approximate rounding features
With approximate rounding, you can enable an approximate clipping to get further improve performance in the case of overflow handling. Approximate clipping enable to discard the extra bit of overflow protection bit in the successor TLU. For consistency a logical clipping is available when this optimization is not suitable.
With approximate rounding, you can enable an approximate clipping to get further improved performance in the case of overflow handling. Approximate clipping enable to discard the extra bit of overflow protection bit in the successor TLU. For consistency a logical clipping is available when this optimization is not suitable.
### Logical clipping

2
docs/execution-analysis/debug.md
View File

@@ -279,7 +279,7 @@ If you cannot find a solution in the community forum, or if you have found a bug
For [bug reports](https://github.com/zama-ai/concrete/issues/new?assignees=&labels=bug%2C+triage&projects=&template=bug_report.md), try to:
* Avoid randomness to ensure reproductibility of the bug
* Avoid randomness to ensure reproducibility of the bug
* Minimize your function while keeping the bug to expedite the fix
* Include your input-set in the issue
* Provide clear reproduction steps