Merge branch 'master' into beam_dev

simonsobs · Sep 9, 2024 · 6d0f64a · 6d0f64a
2 parents ec787f2 + 5afa861
commit 6d0f64a
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/mflike/foreground.py b/mflike/foreground.py
@@ -57,7 +57,7 @@
         nsteps: 1
         bandwidth: 0
 
-If we want to consider it, we have several options on how to compute/read the beam profiles. Notice that we need arrays(freqs, ells+2) (computed from :math:`\ell = 0`), since we want a beam window function for each freq in the bandpasses. We should use this block under ``mflike.BandpowerForeground``:
+If we want to consider the beam chromaticity effect, we have several options on how to compute/read the beam profiles. Notice that we need arrays(freqs, ells+2) (computed from :math:`\ell = 0`), since we want a beam window function for each freq in the bandpasses. We should use this block under ``mflike.BandpowerForeground``:
 
 .. code-block:: yaml
 

diff --git a/mflike/mflike.py b/mflike/mflike.py
@@ -35,7 +35,7 @@
 
 If left ``null``, no systematic template is applied.
 
-The values of the systematic parameters are set in the ``TTTEEE/TTTE/TT/EE/TE/etc.yaml`` fils corresponding to the classes that inherit the ``_MFLike`` one.  They have to be named as
+The values of the systematic parameters are set in the ``TTTEEE/TTTE/TT/EE/TE/etc.yaml`` files corresponding to the classes that inherit the ``_MFLike`` one.  They have to be named as
 ``cal/calT/calE/alpha`` + ``_`` + experiment_channel string (e.g. ``LAT_93/dr6_pa4_f150``).
 """