update(proposals): clarify that prebuilding drivers is on a best-effo…

…rt basis


Signed-off-by: Leonardo Di Donato <leodidonato@gmail.com>
Co-authored-by: Leonardo Grasso <me@leonardograsso.com>

proposals/20200818-artifacts-storage.md

@@ -55,7 +55,7 @@ You can also visualize the full list of prebuilt drivers by driver version visit
 
 ### Notice
 
-The generation of new prebuilt drivers takes usually place with a frequency of 1-2 weeks.
+The generation of new prebuilt drivers takes usually place with a frequency of 1-2 weeks, on a **best-effort** basis.
 
 Thus, it can happen the list of available prebuilt drivers does not yet contain the driver version currently on Falco master.
 
@@ -80,4 +80,4 @@ These images are built and published in two cases:
 - a pull request gets merged into the master branch (**Falco development releases**)
 - a new Falco release (git tag) happens (**Falco stable releases**)
 
-For a detailed explanation of the container images we build and ship look at the following [documentation](https://github.com/falcosecurity/falco/blob/master/docker/README.md).
+For a detailed explanation of the container images we build and ship look at the following [documentation](https://github.com/falcosecurity/falco/blob/master/docker/README.md).