Update some old BuckleScript mentions

Author: chenglou

pages/docs/manual/latest/bind-to-js-function.mdx

@@ -62,7 +62,7 @@ We've compiled to the same function, but now the usage is much clearer on the Re
 
 **Note**: in this particular case, you need a unit, `()` after `border`, since `border` is an [optional argument at the last position](function.md#optional-labeled-arguments). Not having a unit to indicate you've finished applying the function would generate a warning.
 
-Note that you can change the order of labeled arguments on the ReScript side and BuckleScript will ensure that they appear the right way in the JavaScript output:
+Note that you can freely reorder the labels on the ReScript side; they'll always correctly appear in their declaration order in the JavaScript output:
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 
@@ -105,11 +105,11 @@ In a `bs.send`, the object is always the first argument. Actual arguments of the
 
 ### Chaining
 
-Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in BuckleScript too, through the [pipe operator](pipe.md).
+Ever used `foo().bar().baz()` chaining ("fluent api") in JS OOP? We can model that in ReScript too, through the [pipe operator](pipe.md).
 
 ## Variadic Function Arguments
 
-You might have JS functions that take an arbitrary amount of arguments. BuckleScript supports modeling those, under the condition that the arbitrary arguments part is homogenous (aka of the same type). If so, add `bs.variadic` to your `external`.
+You might have JS functions that take an arbitrary amount of arguments. ReScript supports modeling those, under the condition that the arbitrary arguments part is homogenous (aka of the same type). If so, add `bs.variadic` to your `external`.
 
 <CodeTab labels={["ReScript", "JS Output"]}>
 

pages/docs/manual/latest/converting-from-js.mdx

@@ -55,7 +55,7 @@ function queryResult(usePayload, payload) {
 `)
 ```
 ```js
-// Generated by BUCKLESCRIPT, PLEASE EDIT WITH CARE
+// Generated by ReScript, PLEASE EDIT WITH CARE
 'use strict';
 
 const school = require('school');
@@ -110,7 +110,7 @@ function queryResult(usePayload, payload) {
 `)
 ```
 ```js
-// Generated by BUCKLESCRIPT, PLEASE EDIT WITH CARE
+// Generated by ReScript, PLEASE EDIT WITH CARE
 'use strict';
 
 const school = require('school');
@@ -203,7 +203,7 @@ let queryResult = (usePayload, payload) => {
 }
 ```
 ```js
-// Generated by BUCKLESCRIPT, PLEASE EDIT WITH CARE
+// Generated by ReScript, PLEASE EDIT WITH CARE
 'use strict';
 
 var School = require("school");
@@ -258,7 +258,7 @@ let queryResult = (usePayload, payload) => {
 }
 ```
 ```js
-// Generated by BUCKLESCRIPT, PLEASE EDIT WITH CARE
+// Generated by ReScript, PLEASE EDIT WITH CARE
 'use strict';
 
 var School = require("school");

pages/docs/manual/latest/faq.mdx

@@ -20,7 +20,7 @@ BuckleScript is ReScript's old branding, with a sharper focus on proper JS suppo
 
 **What’s the relationship with Reason?**
 
-Reason is a syntax layer for OCaml that BuckleScript also adopted. The current ReScript compiler also supports the old Reason syntax v3.6 for backward compatibility. We will support it for a long time to make sure existing users do not get breaking changes.
+See [here](/bucklescript-rebranding). Reason is a syntax layer for OCaml that BuckleScript also adopted. The current ReScript compiler also supports the old Reason syntax v3.6 for backward compatibility. We will support it for a long time to make sure existing users do not get breaking changes.
 
 **I come from Reason/OCaml. Will ReScript keep supporting X?**
 

pages/docs/manual/v8.0.0/faq.mdx

@@ -16,7 +16,7 @@ We reuse the same excellent type system with OCaml, and lots of other high quali
 
 **What’s the relationship with BuckleScript?**
 
-BuckleScript is ReScript's old branding, with a sharper focus on proper JS support and familiarity which we previously couldn't achieve to the degree we wanted, due to us needing to cater to various different crowds.
+See [here](/bucklescript-rebranding). BuckleScript is ReScript's old branding, with a sharper focus on proper JS support and familiarity which we previously couldn't achieve to the degree we wanted, due to us needing to cater to various different crowds.
 
 **What’s the relationship with Reason?**