Peer Review History
| Original SubmissionFebruary 14, 2025 |
|---|
|
-->PONE-D-25-08162-->-->FtsZ phosphorylation modulates tail-core binding to tune cell division in Bacillus subtilis-->-->PLOS ONE Dear Dr. Mallard, Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.-->--> Please submit your revised manuscript by May 12 2025 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org . When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:-->
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: https://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols . Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols . We look forward to receiving your revised manuscript. Kind regards, Hari S. Misra, Ph.D. Academic Editor PLOS ONE Journal Requirements: When submitting your revision, we need you to address these additional requirements. 1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf 2. PLOS ONE now requires that authors provide the original uncropped and unadjusted images underlying all blot or gel results reported in a submission’s figures or Supporting Information files. This policy and the journal’s other requirements for blot/gel reporting and figure preparation are described in detail at https://journals.plos.org/plosone/s/figures#loc-blot-and-gel-reporting-requirements and https://journals.plos.org/plosone/s/figures#loc-preparing-figures-from-image-files. When you submit your revised manuscript, please ensure that your figures adhere fully to these guidelines and provide the original underlying images for all blot or gel data reported in your submission. See the following link for instructions on providing the original image data: https://journals.plos.org/plosone/s/figures#loc-original-images-for-blots-and-gels. In your cover letter, please note whether your blot/gel image data are in Supporting Information or posted at a public data repository, provide the repository URL if relevant, and provide specific details as to which raw blot/gel images, if any, are not available. Email us at plosone@plos.org if you have any questions. 3. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse. 4. We note that this submission includes NMR spectroscopy data. We would recommend that you include the following information in your methods section or as Supporting Information files: 1) The make/source of the NMR instrument used in your study, as well as the magnetic field strength. For each individual experiment, please also list: the nucleus being measured; the sample concentration; the solvent in which the sample is dissolved and if solvent signal suppression was used; the reference standard and the temperature. 2) A list of the chemical shifts for all compounds characterised by NMR spectroscopy, specifying, where relevant: the chemical shift (δ), the multiplicity and the coupling constants (in Hz), for the appropriate nuclei used for assignment. 3)The full integrated NMR spectrum, clearly labelled with the compound name and chemical structure. We also strongly encourage authors to provide primary NMR data files, in particular for new compounds which have not been characterised in the existing literature. Authors should provide the acquisition data, FID files and processing parameters for each experiment, clearly labelled with the compound name and identifier, as well as a structure file for each provided dataset. See our list of recommended repositories here: https://journals.plos.org/plosone/s/recommended-repositories 5. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions -->Comments to the Author 1. Is the manuscript technically sound, and do the data support the conclusions? The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented. --> Reviewer #1: Yes Reviewer #2: Partly ********** -->2. Has the statistical analysis been performed appropriately and rigorously? --> Reviewer #1: Yes Reviewer #2: Yes ********** -->3. Have the authors made all data underlying the findings in their manuscript fully available? The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.--> Reviewer #1: Yes Reviewer #2: Yes ********** -->4. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.--> Reviewer #1: Yes Reviewer #2: Yes ********** -->5. Review Comments to the Author Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)--> Reviewer #1: Comments to the authors: This manuscript by Mallard and Pham explores an interesting aspect of regulation of FtsZ by phospohorylation. The authors identify S333 residue within the CTL to be phosphorylated in a PrkC kinase dependent manner. They further show that the FtsZ mutants S333A and S333E have enhanced GTPase activity and a lower critical concentration of polymerisation. Accordingly, cell size is also shown to be smaller than WT upon expression of these mutant FtsZs. Alphafold structure predictions and interactions also support the idea that the CTL binds the core region engaging helix H10 and β-strand S9. The CTL peptide is also shown to interact with FtsZ core region by ITC and NMR experiements. Interestingly, the CTL can effectively compete with MinCN for interaction with FtsZ. The findings reported are interesting and suggest a regulatory role for FtsZ phosphorylation in cell cycle in Bacillus subtilis. The conclusions drawn are generally well supported by the experiments and data. While, in support of the article being suitable for publication, I have certain queries. 1.I’m intrigued by the model proposed in Figure 4. The authors mention that when the tail is phosphorylated, intramolecular tail-core interaction is disrupted. Although the authors provide a reasonable structural explanation for the similar defects seen with both S333A and S333E mutations, I think these conclusions may be strengthened by testing the binding of the core residue mutants K335A/H337A to MinCN. One would expect that these mutants are not competed out by the CTL and would these FtsZ mutants be more sensitive to inhibition by MinCN for Z-ring inhibition. 2.Similarly, do S333A and S333E CTL mutants fail to compete with MinCN binding. 3.How does the GTPase activity of FL-FtsZ compare when extrinsic S333A/ E CTL is added? Would it possible to obtain a CTL with Phosphoserine at 333 and compare the differences in the GTPase activity and critical concentration of polymerisation when extrinsically added to FL-FtsZ? I feel, these few in vitro experiments can really add value to the impact of the manuscript before being accepted for publication. 4.Also, although not essential, does depletion of any of the bundlers of FtsZ in S333A and S333E result in restoration of cell length to WT-like? If this not possible to test experimentally, some thoughts of the authors along division ring stabilisation by phosphor regulation could be included in the discussion. Reviewer #2: In this article, the authors convincingly show that the essential cell division protein conserved in nearly all bacteria, FtsZ, is able to autoregulate its enzymatic activity in the Gram-positive model bacterium Bacillus subtilis. This is achieved via a key serine residue (S333) in the intrinsically disordered region which is subject to phosphorylation by a Ser/Thr kinase PrkC. Furthermore, the authors reveal that the disordered C-terminal tail (CTT) is able to compete with a FtsZ regulator (MinC) for the same interaction surface in the FtsZ’s enzymatic core region. Overall, this report provides a valuable insight into the specific role phosphorylation plays in regulating FtsZ in B. subtilis. Moreover, this finding is broadly influential as it provides a plausible explanation regarding the significance of FtsZ phosphorylation reported in multiple species. However, I do have the following concerns which moderately dampened my enthusiasm. Major Comments: 1. Fig. 1E: What is the WT used? Is it bWM200 or PY79? In the text they describe native ftsAZ promoter, is it the strain shown in S5B or S5D? If it is IPTG-inducible ftsAZ, then what concentration was used for expression? Could the authors show a western blot to confirm all three (full-length FtsZ, S333A, S333E) are all produced at similar levels? This is important as slight variations in FtsZ level affect cell length as the authors indicate in the text; and this is the only physiologically relevant data presented in this report. Indicating the strain numbers in the figure legend would be helpful for replicating these results in the future. Is this reproducible in another growth medium such as LB - if not, why? If MinC has unlimited access to FtsZ in S333A/E mutants, then shouldn’t we expect longer cells? 2. ITC experiments: The dissociation constant between Core-CTT and Core-MinC interactions in the nanomolar range seems atypical. Most FtsZ partners are usually in the micromolar range (PMIDs: 22473211; 30636070). Although the following experiment is not needed, a better competition would be with FtsZ core + MinC, and titrating CTT to help support the claim “Surprisingly, MinCN binding was completely abolished when titrated into full-length FtsZ (Fig. 3E, F). This is consistent with the CTT’s higher affinity for the core (Kd = 66 nM vs 111 nM for MinCN).” 3. In the last sentence of Results section, the authors indicate “these results demonstrate direct competition between the tail’s S333 region and MinCN for the C-terminal polymerization surface.” Although plausible, unless the authors make specific mutations in the core to disrupt both MinC and CTT binding, it cannot be argued that this competition is direct. It could possibly be allosteric regulation. 4. In the Discussion: “For filaments, our GTPase assays show S333 mutations affect catalysis, suggesting the tail still binds the core and thus may protect GDP-bound FtsZ interfaces from MinCN, though further structural studies will be needed to confirm this mechanism.” Why is this the case? If S333 mutants do not inhibit the core, higher GTPase activity is expected. The results from this publication may support the notion presented here: PMID: 32198113 (and should be cited). 5. “Whereas its homologs phosphorylate FtsZ in other bacteria (Supp. Table 1), such a direct link to division has not been shown in B. subtilis.” Phosphoproteomics data is experimental evidence, as such it is a direct link. Although, I agree in B. subtilis the explicit connection has not been made. As a side note, it appears that residue T323 is also phosphorylatable (PMID: 34473931). Minor Comments: 1.Line numbering would be useful for making comments. 2.Supplementary figure callouts are not sequential in the text. 3.prkC gene name vs PrkC protein name - standard nomenclature is not being followed. For example, in Fig. 1B it should be ΔprkC. 4.For the phostag gel experiments, I don’t see Halo-S333E in the strain list. 5.NMR: Is there data for phosphomutants to show the chemical shift changes are not observed with a S333 mutant? 6.Selection of H337A needs some introduction. 7.Could helix H10 and beta strand S9 be labeled in the figure? 8.Could the authors discuss the mechanism and/or interaction surface used by MciZ (PMIDs: 25848052; 30636070)? This could add more value to their study if this CTL-core interaction is a general mechanism for competing with negative regulators. Also, how does interaction partners that bind to CTP affect the significance/relevance of phosphorylation (PMID: 23457247)? A brief discussion on this could also be beneficial. 9.Is it possible FtsZ CTT perform intermolecular regulation perhaps in laterally associated protofilaments (in addition to intramolecular as proposed), PMID: 29089389? ********** -->6. PLOS authors have the option to publish the peer review history of their article (what does this mean? ). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy .--> Reviewer #1: No Reviewer #2: No ********** [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/ . PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org . Please note that Supporting Information files do not need this step. |
| Revision 1 |
|
<p>FtsZ phosphorylation modulates tail-core binding to tune cell division in Bacillus subtilis PONE-D-25-08162R1 Dear Dr. Mallard, We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements. Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication. An invoice will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager® and clicking the ‘Update My Information' link at the top of the page. For questions related to billing, please contact billing support . If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. Kind regards, Hari S. Misra, Ph.D. Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-25-08162R1 PLOS One Dear Dr. Mallard, I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS One. Congratulations! Your manuscript is now being handed over to our production team. At this stage, our production department will prepare your paper for publication. This includes ensuring the following: * All references, tables, and figures are properly cited * All relevant supporting information is included in the manuscript submission, * There are no issues that prevent the paper from being properly typeset You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps. Lastly, if your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing. If we can help with anything else, please email us at customercare@plos.org. Thank you for submitting your work to PLOS ONE and supporting open access. Kind regards, PLOS ONE Editorial Office Staff on behalf of Professor Hari S. Misra Academic Editor PLOS One |
Open letter on the publication of peer review reports
PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.
We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.
Learn more at ASAPbio .